> <i>But the other one was just as important: the e1000e driver should never have left its hardware configured in a mode where a single stray write could turn it into a brick.</i><p>... because, like, it's totally <i>okay</i> for the hardware to be bricked by a single stray write?<p>Make like Microsoft and blame the driver. :)<p>It should be a basic manufacturing test to repeatedly write pseudo-random garbage to the entire I/O register space, and check that the hardware never gets into a state that is not recoverable by either a simple power cycle, or, failing that, a factory reset.
Whew, kernel bugs due to complexities of live patching code! (<a href="https://nickdesaulniers.github.io/blog/2020/04/06/off-by-two/" rel="nofollow">https://nickdesaulniers.github.io/blog/2020/04/06/off-by-two...</a>) high fives...anyone...anyone...?
Oh the memories...this was something similar, but just an innocent RESET ATA command.<p><a href="https://www.zdnet.com/article/mandrake-linux-9-2-kills-some-cd-rom-drives/" rel="nofollow">https://www.zdnet.com/article/mandrake-linux-9-2-kills-some-...</a>