From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12272] at random rmmod/insmod corrupts filesystem
Date: Sat, 17 Jan 2009 11:01:06 -0800 (PST) [thread overview]
Message-ID: <20090117190106.4BBA7108040@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12272-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12272
tytso@mit.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|fs_ext3@kernel-bugs.osdl.org|other_modules@kernel-
| |bugs.osdl.org
Severity|normal |low
Component|ext3 |Modules
Product|File System |Other
------- Comment #25 from tytso@mit.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.
prev parent reply other threads:[~2009-01-17 19:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 14:01 [Bug 12272] New: at random rmmod/insmod corrupts filesystem bugme-daemon
2008-12-26 12:11 ` [Bug 12272] " bugme-daemon
2008-12-26 14:16 ` bugme-daemon
2008-12-28 14:47 ` bugme-daemon
2009-01-05 19:52 ` bugme-daemon
2009-01-05 20:11 ` bugme-daemon
2009-01-05 21:50 ` bugme-daemon
2009-01-06 22:21 ` bugme-daemon
2009-01-06 23:57 ` bugme-daemon
2009-01-16 9:48 ` bugme-daemon
2009-01-16 19:37 ` bugme-daemon
2009-01-16 21:24 ` bugme-daemon
2009-01-17 2:23 ` bugme-daemon
2009-01-17 10:29 ` bugme-daemon
2009-01-17 10:34 ` bugme-daemon
2009-01-17 12:59 ` bugme-daemon
2009-01-17 13:47 ` bugme-daemon
2009-01-17 14:12 ` bugme-daemon
2009-01-17 16:13 ` bugme-daemon
2009-01-17 18:24 ` bugme-daemon
2009-01-17 18:27 ` bugme-daemon
2009-01-17 18:40 ` bugme-daemon
2009-01-17 18:43 ` bugme-daemon
2009-01-17 18:46 ` bugme-daemon
2009-01-17 18:56 ` bugme-daemon
2009-01-17 19:01 ` bugme-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090117190106.4BBA7108040@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.