| 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
| ||
|
Message-Id: <201011191602.oAJG2ucH029949@demeter1.kernel.org> Date: Fri, 19 Nov 2010 16:02:56 GMT From: bugzilla-daemon@...zilla.kernel.org To: linux-ext4@...r.kernel.org Subject: [Bug 23232] kernel hang on insert ext4 usb key https://bugzilla.kernel.org/show_bug.cgi?id=23232 --- Comment #9 from Theodore Tso <tytso@....edu> 2010-11-19 16:02:53 --- I'm not convinced we even got into the ext4_fill_super(); if we did there should have been at least some ext4 printk's. The OOPS is in vfs_kern_mount(). I've looked through ext4_fill_super(), and if vfs_kern_mount() had gotten as far as calling into ext4_fill_super(), I can't find any code path other than failing the first two memory allocations that wouldn't have resulted in some kind of kernel printk --- which wasn't in the oops display. So I strongly suspect the failure was before vfs_kern_mount() calling ext4_mount(), or in mount_bdev() --- since all ext4_mount() does is call mount_bdev() passing in ext4_fill_super as a callback function. Can the oops be replicated at this point? If so, we can try instrumenting the kernel, but this strongly smells like a hardware problem and a failure in the generic code before we drop into the ext4 mount code in ext4_fill_super(). -- Ted -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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