| 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
| ||
|
Message-ID: <20100708144317.GA2364@kroah.com> Date: Thu, 8 Jul 2010 07:43:17 -0700 From: Greg KH <greg@...ah.com> To: Tvrtko Ursulin <tvrtko.ursulin@...hos.com> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Al Viro <viro@...iv.linux.org.uk> Subject: Re: BUG: Securityfs and bind mounts (2.6.34) On Thu, Jul 08, 2010 at 11:12:41AM +0100, Tvrtko Ursulin wrote: > > Hi guys, > > If I overlay a file in securityfs using mount --bind with a file from > a regular filesystem, should I be allowed to rmmod the module which > registered the overlaid securityfs file? Why would you want to overlay securityfs in the first place? And you might be able to rmmod the module, but I didn't think that security modules were able to be unloaded anymore. > I was able to do that, then I > unmounted the bind mount, and then when attempting to unmount > securityfs hit a BUG at > fs/dcache.c:676 (see below). It would have made more sense to first > umount the overlay file and then remove the module which registered > with securityfs, nevertheless should kernel crash in this case? Probably not, but then again, you did something that you shouldn't have, so perhaps it is telling you not to do such a thing in the future :) thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists