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 for Android: free password hash cracker in your pocket

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

Message-Id: <20090117184609.5B7D510800D@picon.linux-foundation.org>
Date:	Sat, 17 Jan 2009 10:46: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 #23 from devzero@....de  2009-01-17 10:46 -------
>Note that it is not necessarily guaranteed to be safe to be unloading modules. 

if it`s not safe, those unsafe modules should be marked appropriately that
they cannot be unloaded. at least they should spit out a warning that unloading
should be avoided. there are already lot`s of modules which cannot be
unloaded at all, so it`s just a matter of good will if the others being marked
appropriately. 

if a module is unloadable and this is unsafe and if that module doesn`t tell
that to the user, then i`d call that a bug.
if it DOES tell that and the kernel crashes, then it`s user error.

why i think this way?
i already did lot`s of module testing like this user does, so i did lot`s of
automated module load unload and found the one or other bug with this, but it`s
the first time that someone is telling, that this should NOT be done because
there are developers who do not support this.

i think it`s good that we have people like folkert reporting such issues,
because it enhances kernel quality.

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