On Mon, Mar 24, 2008 at 01:50:14AM -0700, Ram Pai wrote: > > Is there any reason why we do that in ->umount_begin() and not *after* > > it, unconditionally, straight from do_umount()? AFAICS, the only reason > > why it's done from fs-specific code is figuring out which mount-list > > should the stuff go back to, and that's both broken *and* not needed > > with sanitized locking as above. While we are at it, I'd rather return > > ->umount_begin() to its previous prototype, TYVM - the less filesystem > > sees vfsmounts, the better off we all are... > > I think that ->umount_begin also acts a hook for providing pre-umount > event notification to userspace from filesystems; something that is > required by DMAPI interface. "Why, so can I, and so can any man..." IOW, DMAPI might require whatever its authors want it to require, but what does that have to do with us? BTW, I've dropped several more patches into the tree (sanitizing namespace.c/pnode.c) and merged that into mountinfo-base. Documentation is mostly done, so it will be the next thing to go there, then it's time for 'dissolve unreachable subtrees on d_invalidate()' stuff. Which probably will mean *another* cyclic list in vfsmount, not anchored but pointed to by replacement of d_mounted; same protection as for mnt_child/mnt_mounts, contains vfsmounts with given mnt_mountpoint. I'm not too fond of that, but I don't see cleaner way to do it at the moment. Any better ideas are welcome... -- 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
