| Summary: | kernel 3.13.6 - mounting VFAT formatted USB storage causes segmentation fault in parse_options+[...] [fat] | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sandu Adrian <adrian.sandu> |
| Component: | [OLD] Core system | Assignee: | Justin Lecher (RETIRED) <jlec> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | CC: | adrian.sandu, alex_y_xu |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Sandu Adrian
2014-03-18 16:47:02 UTC
d3xt3r01 ~ # ps ax -o comm,wchan | grep mount mount call_rwsem_down_write_failed mount mount_bdev I'm pretty sure we don't support out-of-tree kernel modules. Is the vfat out of tree ? Mar 18 18:43:17 d3xt3r01 kernel: [200072.029486] Modules linked in: vfat fat aufs(O) snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep e1000e nuvoton_cir rc_core x86_pkg_temp_thermal coretemp e1000 fuse ext2 It's a module.. I don't get the "out of tree" part ... It seems there's something more than this .. another ntfs drive I had gets the same treatment .. d3xt3r01 media # mount /dev/sdj1 wireless/ d3xt3r01 media # ls Killed d3xt3r01 media # ls Killed d3xt3r01 media # cd /media/wire[TAB_KEY] dexter@d3xt3r01 $ It seems it killed the sudo/sh whatever session and returned me to the user :| dexter@d3xt3r01 $ mount | grep wireless /dev/sdj1 on /media/wireless type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096) There is definetly something wrong here .. can't figure out what though .. Mar 21 13:59:45 d3xt3r01 kernel: [227303.434985] PGD 10a1b7067 PUD 100247067 PMD 0 Mar 21 13:59:45 d3xt3r01 kernel: [227303.435659] Oops: 0000 [#6] SMP Mar 21 13:59:45 d3xt3r01 kernel: [227303.436342] Modules linked in: aufs(O) snd_usb_audio snd_usbmidi_lib snd_rawmidi e1000e snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_intel snd_hda_codec x86_pkg_temp_thermal coretemp nuvoton_cir rc_core snd_hwdep e1000 fuse ext2 Mar 21 13:59:45 d3xt3r01 kernel: [227303.437831] CPU: 1 PID: 20280 Comm: ls Tainted: G D O 3.13.6-gentoo #5 Mar 21 13:59:45 d3xt3r01 kernel: [227303.438530] Hardware name: /D54250WYK, BIOS WYLPT10H.86A.0024.2014.0210.1909 02/10/2014 Mar 21 13:59:45 d3xt3r01 kernel: [227303.439240] task: ffff88007b32e3f0 ti: ffff88009da0a000 task.ti: ffff88009da0a000 Mar 21 13:59:45 d3xt3r01 kernel: [227303.439949] RIP: 0010:[<ffffffffa0013015>] [<ffffffffa0013015>] fuse_req_init_context+0x15/0x50 [fuse] Mar 21 13:59:45 d3xt3r01 kernel: [227303.440646] RSP: 0018:ffff88009da0bca0 EFLAGS: 00010246 Mar 21 13:59:45 d3xt3r01 kernel: [227303.441346] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000 Mar 21 13:59:45 d3xt3r01 kernel: [227303.442043] RDX: ffff88007b32e3f0 RSI: ffffffffa00224f0 RDI: ffff8800bfc42660 Mar 21 13:59:45 d3xt3r01 kernel: [227303.442722] RBP: ffff88009da0bd18 R08: 0000000000000000 R09: ffff8800bfc427b0 Mar 21 13:59:45 d3xt3r01 kernel: [227303.443396] R10: 0000000000000000 R11: ffffea000008be00 R12: 0000000000000000 Mar 21 13:59:45 d3xt3r01 kernel: [227303.444082] R13: ffff88009da0bef0 R14: ffff8800c9cf8000 R15: ffff880097534000 Mar 21 13:59:45 d3xt3r01 kernel: [227303.444769] FS: 00007fe1ea1e1700(0000) GS:ffff88011fa80000(0000) knlGS:0000000000000000 Mar 21 13:59:45 d3xt3r01 kernel: [227303.445440] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 21 13:59:45 d3xt3r01 kernel: [227303.446132] CR2: 000000000000001c CR3: 000000010d55b000 CR4: 00000000001407e0 Mar 21 13:59:45 d3xt3r01 kernel: [227303.446825] Stack: Mar 21 13:59:45 d3xt3r01 kernel: [227303.447480] ffffffffa001404d ffff8800bfc42660 000000007b32e3f0 ffff88006adbd3c0 Mar 21 13:59:45 d3xt3r01 kernel: [227303.448182] ffff88011fdfac00 ffffea0000075e40 0000000000000000 ffff8800c9cf8000 Mar 21 13:59:45 d3xt3r01 kernel: [227303.448877] ffffffff810f2d12 ffff8800d6ce6520 ffff8800c9cf8000 ffff880097534000 Mar 21 13:59:45 d3xt3r01 kernel: [227303.449542] Call Trace: Mar 21 13:59:45 d3xt3r01 kernel: [227303.450223] [<ffffffffa001404d>] ? __fuse_get_req+0x18d/0x260 [fuse] Mar 21 13:59:45 d3xt3r01 kernel: [227303.450917] [<ffffffff810f2d12>] ? unlock_page+0x22/0x30 Mar 21 13:59:45 d3xt3r01 kernel: [227303.451581] [<ffffffffa001413b>] fuse_get_req+0xb/0x10 [fuse] Mar 21 13:59:45 d3xt3r01 kernel: [227303.452262] [<ffffffffa00182bd>] fuse_do_getattr+0x3d/0x280 [fuse] Mar 21 13:59:45 d3xt3r01 kernel: [227303.452943] [<ffffffff8114d101>] ? final_putname+0x21/0x50 Mar 21 13:59:45 d3xt3r01 kernel: [227303.453598] [<ffffffff8114d2f6>] ? putname+0x26/0x40 Mar 21 13:59:45 d3xt3r01 kernel: [227303.454273] [<ffffffff81152245>] ? user_path_at_empty+0x95/0x100 Mar 21 13:59:45 d3xt3r01 kernel: [227303.454952] [<ffffffffa0019195>] fuse_update_attributes+0x85/0x90 [fuse] Mar 21 13:59:45 d3xt3r01 kernel: [227303.455614] [<ffffffffa0019591>] fuse_getattr+0x41/0x50 [fuse] Mar 21 13:59:45 d3xt3r01 kernel: [227303.456294] [<ffffffff81146974>] vfs_getattr_nosec+0x24/0x40 Mar 21 13:59:45 d3xt3r01 kernel: [227303.456974] [<ffffffff81146d51>] vfs_getattr+0x31/0x40 Mar 21 13:59:45 d3xt3r01 kernel: [227303.457625] [<ffffffff81146dbc>] vfs_fstatat+0x5c/0xa0 Mar 21 13:59:45 d3xt3r01 kernel: [227303.458294] [<ffffffff81146e49>] vfs_lstat+0x19/0x20 Mar 21 13:59:45 d3xt3r01 kernel: [227303.458962] [<ffffffff81146e65>] SYSC_newlstat+0x15/0x30 Mar 21 13:59:45 d3xt3r01 kernel: [227303.459611] [<ffffffff81147149>] SyS_newlstat+0x9/0x10 Mar 21 13:59:45 d3xt3r01 kernel: [227303.460286] [<ffffffff81750f62>] system_call_fastpath+0x16/0x1b Mar 21 13:59:45 d3xt3r01 kernel: [227303.460963] Code: <8b> 40 1c 83 f8 ff 0f 44 05 4a fd c1 e1 89 47 50 48 8b 82 78 04 00 Mar 21 13:59:45 d3xt3r01 kernel: [227303.462363] RSP <ffff88009da0bca0> Mar 21 13:59:45 d3xt3r01 kernel: [227303.463049] CR2: 000000000000001c Mar 21 13:59:45 d3xt3r01 kernel: [227303.463723] ---[ end trace dbd4bf838f35b332 ]--- Same thing happens in 3.12.13 too ! Oh, O is oops, not out-of-tree. Sorry. No, 'D' means oops, 'O' means out-of-tree. I think we only support aufs as part of aufs-sources. Worked ok 'till I migrated to the new intel nuc ( I had an asrock 152d before ). Still, why do you think it would be aufs's fault ? Does this also happen with gentoo.sources? Please try this and report it here. By gentoo.sources I think you mean gentoo-sources, right ? emerge: there are no ebuilds to satisfy "gentoo.sources". The initial bug report was for sys-kernel/gentoo-sources-3.13.6 You think it was fixed in 3.13.7 ? Meaning without external patches or modules. |
