On Tue, Oct 05, 2010 at 12:31:15PM +0200, Miklos Szeredi wrote: > From: Miklos Szeredi <mszeredi@xxxxxxx> > > Currently remouting superblock read-only is racy in a major way. > > With the per mount read-only infrastructure it is now possible to > prevent most races, which this patch attempts. > > Before starting the remount read-only, set MNT_WRITE_HOLD on all > mounts so that writes are held off until the remount either succeeds > or fails. Umm... What'll happen if your remount will say mnt_want_write() on e.g. internal vfsmount over that sb? Or, more subtle, tries to update atime on some opened struct file on that sb. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
