On Tue, Mar 22, 2005 at 12:24:37PM +1100, Greg Banks wrote: > G'day, > > The attached patch fixes a bug in the VFS code which causes > "Busy inodes after unmount" and a subsequent oops.
Applied, thanks. > > Greg. > -- > Greg Banks, R&D Software Engineer, SGI Australian Software Group. > I don't speak for SGI. > > Following an absolute symlink opens a window during which the > filesystem containing the symlink has an outstanding dentry count > and no outstanding vfsmount count. A umount() of the filesystem can > (incorrectly) proceed, resulting in the "Busy inodes after unmount" > message and an oops shortly thereafter. > > Systems using autofs-controlled NFS mounts are especially vulnerable, > as autofs both increases the number of unmounts happening and does NFS > mounting in response to lookups which can result in multiple-second > vulnerability windows. However the bug could happen on any filesystem. > > This patch adds a mntget()/mntput() pair around the link following code > (as the 2.6 code does). Attempts to umount() during link following > now return EBUSY. > > > Signed-off-by: Greg Banks <[EMAIL PROTECTED]> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
