From: Al Viro <viro@ZenIV.linux.org.uk>
To: lsf10-pc@lists.linuxfoundation.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [topic proposal] dealing with ->d_revalidate() right ways (automounting, atomic opens and the whole mess around that)
Date: Wed, 9 Jun 2010 03:19:40 +0100 [thread overview]
Message-ID: <20100609021940.GW31073@ZenIV.linux.org.uk> (raw)
That's going to be the next big change of VFS architecture; bits
and pieces had been discussed on lists and in private mail, but it would
be really useful to sit down and discuss that face to face with everyone
involved.
* ->follow_link() is abused for triggering submounts.
* ->d_revalidate() is abused in many, _many_ ways, including
autofs, NFS "reval_dot" stuff, atomic opens, etc. Moreover, it has nasty
interplay with crossing mountpoints.
* NFS handling of atomic opens is near the point where we can
switch to methods that would get proper arguments directly, rather
than abusing ->lookup/->d_revalidate/whatnot. Again, ->d_revalidate
and mountpoint crossing are stumbling blocks. And NFS4 bits around
open are just plain scary...
* NFSv4 has rather unpleasant stuff in submount handling - what
it does with ->mnt_devname doesn't bear describing in polite company and
it actually doesn't work right with mount --bind (moderately) and
mountinfo contents (completely). Both issues are fixable and that gets
entangled into the aforementioned ball of barbed wire...
Who might want to be there: nfsd/nfs/cifs/afs/autofs4 and general
VFS-interested folks.
next reply other threads:[~2010-06-09 2:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 2:19 Al Viro [this message]
2010-06-09 2:29 ` [topic proposal] dealing with ->d_revalidate() right ways (automounting, atomic opens and the whole mess around that) Joel Becker
2010-06-14 14:40 ` Trond Myklebust
2010-06-21 20:54 ` Frank Mayhar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100609021940.GW31073@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf10-pc@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.