On Sat, Aug 11, 2018 at 09:31:29AM -0700, Andy Lutomirski wrote:

> I don’t see why we need all this fancy “do the options match” stuff.  For the 
> handful of filesystems (like NFS) that do something intelligent when multiple 
> non-bind mount requests against the same underlying storage happen,  we can 
> keep that behavior in the new API. For other filesystems that don’t have this 
> feature, we should simply fail the request.

> IOW I see so compelling reason to call sget() at all from the new API.  The 
> only sort-of-legit use case I can think of is mounting more than one btrfs 
> subvolume. But even that should probably not be done by asking the kernel to 
> separately instantiate the filesystem.


May I politely suggest the esteemed participants of that conversation
to RTFS?  Yes, I know that it's less fun that talking about your
rather vague ideas of how the things (surely) work, but it just might
avoid the feats of idiocy like the above.

Andy, I don't know how to put it more plainly: read the fucking source.
Even grep would do.  The same NFS you've granted (among the "handful"
of filesystems) an exception, *DOES* *CALL* *THE* *FUCKING* sget().

Yes, really.  And in some obscure[1] cases (including the one mentioned
upthread) it does reuse a pre-existing superblock.  For a very good
reason.

[1] such as, oh, mounting two filesystems from the same server with
default options - who would've ever thought of doing something so
perverted?

_______________________________________________
tomoyo-dev-en mailing list
tomoyo-dev-en@lists.osdn.me
https://lists.osdn.me/mailman/listinfo/tomoyo-dev-en

Reply via email to