On Thu, Apr 24, 2008 at 04:58:00PM +0200, Miklos Szeredi wrote: > Since all the vfs_* functions will become static with path_* being the > only caller, the compiler will be happy to get rid of that stack frame > too. > > What is left is the guarantee, that the race-free r/o remounts will > always work and some obscure caller didn't forget to surround it with > the r/o checks. > > I think it's definitely worth it. It would be, if we had only single vfs_...() as critical sections. We do not - see previous mail or read the fucking tree, already. We don't even have many callers of each, and with a few we do it's not obvious that we want to go through vfsmounts (and vfsmount-based checks) in all of them. So no, I don't buy your argument. Sorry. I'm not even convinced that they are useful as helpers, at least until we'd decided what to do with checks in nfsd. Until then we do, as far as I'm concerned, one place where they would definitely DTRT - fs/namei.c. And I want more than one caller before merging those, let alone removing the interface that doesn't require checks to be vfsmount-based for all users. -- 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
