linux-ext4 - [Bug 12272] at random rmmod/insmod corrupts filesystem

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 16 Jan 2009 18:23:09 -0800 (PST)
From:	bugme-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 12272] at random rmmod/insmod corrupts filesystem

http://bugzilla.kernel.org/show_bug.cgi?id=12272





------- Comment #12 from tytso@....edu  2009-01-16 18:23 -------
It's still not clear to me what you do to trigger the corruption.  What
modules, specifically, are you removing and inserting?   Can you narrow it down
to a single module?

The messages

[  487.377387] bio too big device hda5 (8 > 0)
[  487.377860] bio too big device hda5 (8 > 0)

... indicates that the block queue data structure has gotten corrupted (since
queue->max_hw_sectors should never be zero).   Bottom line is it sounds like
*some* module is causing random memory corruption, leading to the kernel
malfunctioning.   The bottom line is figuring out which kernel module or
modules are involved.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
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