Fine, then the ATA specification is broken instead of the disk hardware.
If the ATA specification mandates that compliant drives contain the
equivalent of a self-destruct command, then this isn't a problem with
the Linux kernel. Even if the IDE driver in the kernel has checks to
prevent the self-destruct command from being sent to the drive via
normal IDE driver operations, this can't guarantee that the
self-destruct command can never be sent to the drive; malicious kernel
code or root-run programs will still be able to deliver the command
directly to the drive without going through the IDE driver.
Can we just be done with this now? This is by no means the first or the
worst case where bad kernel code or incompetence or malice on the part
of a root user can damage hardware devices beyond repair. If there's an
earth-shattering revelation here, it's that the ATA specification is
fundamentally flawed and needs to be fixed for there to be a real
solution to this problem.
And please, Andre, count to 10 and relax a bit before sending your
replies. Practically all I've seen from you on this is hysterical and
sometimes incomprehensible ranting, and gratuitous insults directed
towards even the most reasoned respondents. If you just calmly
explained the exact nature of the problem in the ATA specification, it
would help us all figure out what solution, if any, could be applied to
the problem in the Linux kernel.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/