On Thu, Jan 09, 2014 at 11:05:45AM -0500, Eric Paris wrote: > [adding lsm and selinux] > > Am I just crazy, or was this bug discussed (and obviously not fixed) > some time ago? > > VFS can still use inodes after security_inode_free_security() was > called... Unrelated bug. > > Assuming the VFS guys say that delaying __destroy_inode() is safe like > > that, I like it better. It also means that this is fixed for all LSMs, > > not just SELinux... Recall what your own code called from __destroy_inode() (fsnotify horrors) is doing - you can't grab a mutex from RCU callback... -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html