... which will do horrible things to your device, because it's essentially asking to remove the wheels off of a running car without the car and/or driver being aware of it, and as such having time to park and ask its passengers to step out. (Hey, my crappy analogy for impromptu USBMS almost makes sense
).
That said, I'm genuinely curious as to what was your experience before this fix, because what happened up until now perfectly falls into the mysterious realm of "undefined behavior".
(And most likely veering into the "oh shit" side of "undefined behavior").
At the very least, KOReader crashed. At worst, the kernel hung. In between there, you could experience a volumd and/or awesome induced softlock. Any of these could potentially be cause for data loss and/or filesystem curruption.
So, yeah, genuinely curious as to how your device behaved
.
Because, agreed, it's a pretty harsh way of avoiding the problem, but I'm not seeing any better ways to avoid the worst on unsuspecting users, unfortunately ;/.