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]

Message-Id: <20090117134746.2E70A108042@picon.linux-foundation.org>
Date:	Sat, 17 Jan 2009 05:47:46 -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 #16 from tytso@....edu  2009-01-17 05:47 -------
Well, the first thing I would do is optimize the test-cycle.   I would create
partition the disk so you can install a stable debian system (I think you said
you were stable with 2.6.26?), a fixed image of your test system (using 2.6.28
or 2.6.29-rc1), using the smallest posible system you can that still reproduces
the problem.    Then copy, using dd, the fixed image of the test system to the
scratch partition, and then rig up grub (where the menu.conf file is on your
stable system) so you can boot the scratch partition.   Hopefully that way you
can cut down your test cycle down to 5-10 minutes.


-- 
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