From: Mikulas Patocka <mpatocka@xxxxxxxxxx> Date: Sat, 7 Nov 2009 00:36:23 -0500 (EST) > - If the controller corrupted common kernel data, the bug would show on > all processes or on all "vmstat" processes and it wouldn't go away after > clearing disk cache. Not necessarily true. I suspect the corrupted directory page ext3 was accessing caused it to walk to arbitrary parts of kernel ram and corrupt it. So only a program which accessed specific files would get us into that corruption situation. It could be anything. Surely we could add more protection and careful assertions into the ext2/ext3/ext4 directory entry traversing code (check for unaligned offsets etc.) -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
