Re: [RFC][PATCHSET v3] non-recursive pathname resolution & RCU symlinks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Al Viro <viro@xxxxxxxxxxxxxxxxxx> writes:

> In particular, automounts will require
> discussing what exactly in the process' state is used for those - both
> with autofs/NFS/AFS/CIFS folks and with Eric (what netns should be used
> when we are crossing an NFSv4 referral point? Should it come from the
> NFS mount we'd found the referral on, or from the process that has run
> across it?  There'd been a series from Ian around the interplay of
> autofs with namespaces, and IIRC it stepped into similar-sounding areas;
> it'll need to be looked into, etc.)

Almost certainly it should be the netns of NFS mount the referral
is on.

Looking at processes causes all kinds of caching problems, and is only
really appropriate when we are looking at something deliberate like
magic symlinks (i.e. /proc/self).

Automounts are the one case where I can image capturing the current
netns during mounting of the filesystem could be an issue.

Eric
--
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




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux