[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20090117190106.4BBA7108040@picon.linux-foundation.org>
Date: Sat, 17 Jan 2009 11:01:06 -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
tytso@....edu changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|fs_ext3@...nel-bugs.osdl.org|other_modules@...nel-
| |bugs.osdl.org
Severity|normal |low
Component|ext3 |Modules
Product|File System |Other
------- Comment #25 from tytso@....edu 2009-01-17 11:01 -------
I agree this would be a desirable thing to do, but it takes time for this to
happen, and the people who are most interested in determining which modules are
runing into problems when unloaded frequently are the ones who need to do this
testing.
I'll note there are also those modules which *can* be safely unloaded, as long
as you ifconfig down the interface, make sure there are no active programs
accessing them, wait a few seconds, (save your files just in case), and then
unload it, while crossing your fingers. It's sufficiently useful to unload
this driver that even though you have to be ***very*** careful to unload it,
I'd prefer that it not be made completely impossible to remove. Note that
there already is a config option to prevent rmmod from working at all, and
rmmod requires root privs, and we do expect root to have at least some
background skills....
--
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.
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
Powered by blists - more mailing lists