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.
I'm not sure who is at fault here, possible options I see are: kernel, gcc
or hardening. Any help is appreciated; if I should supply any additional
information please ask.
Markus Oehme
PS: Please cc me since I'm not subscribed to the list.
=== o>< ========================
[ 4365.087646] invalid opcode: 0000 [#110] SMP
[ 4365.088001] Modules linked in:
[ 4365.088001] CPU 2
[ 4365.088001] Pid: 7253, comm: sh Tainted: G D 3.6.6-hardened #1 /DP45SG
[ 4365.088001] RIP: 0010:[<ffffffff8114a0fe>] [<ffffffff8114a0fe>] iov_iter_advance+0x3e/0xb0
[ 4365.088001] RSP: 0018:ffff8801fc989a38 EFLAGS: 00010297
[ 4365.088001] RAX: 0000000000000031 RBX: ffff8801fc989ac8 RCX: 00000000007278be
[ 4365.088001] RDX: 0000000000000000 RSI: 00000000019dadfb RDI: ffff8801fc989ac8
[ 4365.088001] RBP: ffff8801fc989a48 R08: 0000000000014d70 R09: ffff88022fd14d70
[ 4365.088001] R10: 00000000019dadfb R11: 0000835a83413d99 R12: 00000000019dadfb
[ 4365.088001] R13: 0000000000000fcd R14: ffff880081431548 R15: 00000000019dadfb
[ 4365.088001] FS: 0000035b026c0700(0000) GS:ffff88022fd00000(0000) knlGS:0000000000000000
[ 4365.088001] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4365.088001] CR2: 0000075b019dade5 CR3: 00000000019f9000 CR4: 00000000000407f0
[ 4365.088001] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 4365.088001] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 4365.088001] Process sh (pid: 7253, threadinfo ffff880081431548, task ffff880081431040)
[ 4365.088001] Stack:
[ 4365.088001] 0000000000000033 0000000000000031 ffff8801fc989b18 ffffffff8114a715
[ 4365.088001] 0000000000000000 ffffffff811cfe0c ffff8801cd2958f8 ffff8801fc989d58
[ 4365.088001] 0000000000000033 ffff880081431040 00000000fc989ab8 ffffffff81abf3c0
[ 4365.088001] Call Trace:
[ 4365.088001] [<ffffffff8114a715>] generic_file_buffered_write+0x195/0x280
[ 4365.088001] [<ffffffff811cfe0c>] ? __mark_inode_dirty+0x11c/0x220
[ 4365.088001] [<ffffffff8114c645>] __generic_file_aio_write+0x225/0x420
[ 4365.088001] [<ffffffff8114c8bd>] generic_file_aio_write+0x7d/0xf0
[ 4365.088001] [<ffffffff81246db9>] ext4_file_write+0xa9/0x490
[ 4365.088001] [<ffffffff81246d10>] ? ext4_file_mmap+0x70/0x70
[ 4365.088001] [<ffffffff811a29ab>] do_sync_readv_writev+0xbb/0x100
[ 4365.088001] [<ffffffff811a2eea>] do_readv_writev+0xda/0x1f0
[ 4365.088001] [<ffffffff811a3050>] vfs_writev+0x50/0x90
[ 4365.088001] [<ffffffff811a320a>] sys_writev+0x4a/0xb0
[ 4365.088001] [<ffffffff819e5de7>] system_call_fastpath+0x1c/0x21
[ 4365.088001] Code: 49 89 f4 48 8b 43 18 4c 39 e0 72 1f 48 8b 53 08 48 83 fa 01 75 17 4c 01 63 10 4c 29 e0 48 89 43 18 48 8b 5d f0 4c 8b 65 f8 c9 c3 <0f> 0b 48 8b 33 48 8b 4b 10 4d 85 e4 75 12 48 85 c0 75 4d 48 89
[ 4365.088001] RIP [<ffffffff8114a0fe>] iov_iter_advance+0x3e/0xb0
[ 4365.088001] RSP <ffff8801fc989a38>
[ 4365.135449] ---[ end trace 9363d5d9523cd314 ]---
=== o>< ========================
--
Aoccdrnig to a threoy, it deosn't mttaer in waht oredr the ltteers in a wrod
are, the olny iprmoatnt tihng is taht the frist and lsat ltteer are in the
rghit pclae. The rset can be a taotl mses and you can sitll raed it in msot
csaes. Tihs is bcuseae the huamn mnid deos not raed ervey lteter by istlef,
but the wrod as a wlohe. And I awlyas thought slpeling was ipmorantt.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
