[lkml]   [2000]   [Jul]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: TO HELL WITH IT THEN......(re: disk-destroyer.c)

Although I think we all respect your role as an IDE god, I personally
believe your off base on this particular issue. It is not the kernel's
role to decide which device access patterns are legal, and which are
not. If such policy is going to be put in place, it should be at the
application level if anywhere.

The rest of the kernel seems to obey this philosophy. For instance,
/dev/kmem does not attempt to restrict memory access to areas that can
only be used to cause harm, and /dev/nvram doesn't prevent you from
overwriting critical NVRAM data with garbage. Using the PPro microcode
driver, I could create cpu-destroyer.c. It wouldn't prove that the
microcode driver needs to verify data passing through it.

The last thing the kernel needs to do is protect hardware from root's


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:57    [W:0.160 / U:23.160 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site