| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sat, 5 Jun 2010 16:57:33 -0600 From: Jeffrey Merkey <jeffmerkey@...il.com> To: linux-kernel@...r.kernel.org Subject: 2.6.34 general comments Seeing a lot of file system corruption with temporary files on EXT3. /root/.viminfo gets trashed a lot if the system is not shut down. EXT3 recovery during boot produces corrupted files. Does not happen on 2.6.28. Seeing system lockups on my Compaq Presario 2200 even after just letting it boot up and not even logging in. Seeing the /boot/grub/grub.conf file getting trashed and replaced with binary junk during EXT3 recovery if system not shutdown properly. At any rate, I am not accustomed to seeing file system corruption in EXT3 like I am seeing even when I abuse the shit out of the system like I normally do during development of kernel modules. Overall, performance on 2.6.34 is a lot better then I have ever seen before on Linux with disk I/O and the kernel behaves a lot better with heavy IO. So that's a plus. Also, the hw_breakpoint subsystem has a lot of issues with other debuggers using the notify_die handlers since it hooks first. resident debuggers are just broken if it is left active. Clearing of DR6 in traps.c under x86 also is troublesome and will break any loadable debugger. a better approach may be needed. Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists