| 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: Mon, 12 Nov 2012 09:54:33 -0500 From: Theodore Ts'o <tytso@....edu> To: Markus Oehme <oehme.markus@....de> Cc: linux-ext4@...r.kernel.org Subject: Re: Kernel Errors: Wrong Opcodes On Mon, Nov 12, 2012 at 02:56:23PM +0100, Markus Oehme wrote: > Hello, > > I see lots of the following errors on my amd64 machine under heavy load > (specifically the gcc test suite). Since the trace mentions ext4 I decided > to send this to the ext4 mailing list. > > The scenario: I'm running a Hardened Gentoo ~amd64 (Intel Core2 Quad) box > with gcc-4.7.2 and Linux 3.6.6 with hardening patches (grsec). During a > build from source of gcc-4.7.2 the error prints to the console, specifically > this seems to occur during the test phase. There are multiple instances of > the error all with the same call trace. The computer stays usable, but the > build directory of the gcc build is somehow damaged. It is afterwards > impossible to delete the build directory (rm simply hangs forever) until I > reboot the machine. After the reboot everything seems to be fine again. Invalid opcode sure sounds like it's a compiler issue. Since you can relatively easily reproduce this, can you try recompiling a kernel w/o hardening, and see if the problem goes away? If it does, you can send a bug report to the GCC folks. Regards, - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists