From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.com>
Cc: Steve Dickson <SteveD@redhat.com>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/7] Assorted mount/mountd nfs-utils patches - V2
Date: Fri, 29 Jul 2016 15:05:41 -0400 [thread overview]
Message-ID: <20160729190541.GC7964@fieldses.org> (raw)
In-Reply-To: <146976807524.20186.8871903418718212567.stgit@noble>
ACK to the series.
On Fri, Jul 29, 2016 at 03:03:36PM +1000, NeilBrown wrote:
> Hi,
> here is a revision of a recent patch series.
> Thanks to Bruce's uncompromising review I have significantly reduced
> the changes to mountpoint handling to just that which is needed.
>
> If we assume the NFSv3 behavior is "correct" (because it has been
> that way for over a decade), the NFSv4 behavior differs
> particularly in that a mount request arrives as a lookup from an
> pseduo-root parent. This is seen by rpc.mountd as an upcall through
> nfsd.export.
> The nfsd_export() handled was ignoring the mountpoint option, and
> that is incorrect. So a patch in this series handles the option correctly.
>
> The changes to blocking and ESTALE return, and the monitoring of
> /proc/mounts have all been removed.
>
> It might be beneficial to change the kernel so that the reported
> mtime of V4ROOT directories is that last time any change was made to
> any V4ROOT export. That might allow the client to see changes in
> exports more quickly.
>
> It might also be generally useful for mountd to monitor /proc/mounts
> (using e.g. select()) and flush the export cache shortly after any
> changes. Again, this would allow the client to see changes more
> promptly.
>
> However I don't plan either of these immediately, which means they
> almost certainly won't happen unless the issue is raised again for
> some reason.
Makes sense, thanks.--b.
>
> Thanks,
> NeilBrown
>
> ---
>
> NeilBrown (7):
> nfs.man: clarify effect of 'retry' option.
> mountd: remove the --exports-file option
> mount: don't treat temporary name resolution failure as permanent.
> mount: use a public address for IPv6 callback.
> mount: fix memory leak in v4root_add_parents
> mountd: allow alternate ttl to be specified for dump_to_cache.
> mountd: fail nfsd.export lookup for path to unmounted exportpoint
>
>
> utils/mount/network.c | 5 ++++
> utils/mount/nfs.man | 14 ++++++++++--
> utils/mount/stropts.c | 54 +++++++++++++++++++++++++++--------------------
> utils/mountd/auth.c | 5 +---
> utils/mountd/cache.c | 36 ++++++++++++++++++++++++-------
> utils/mountd/mountd.c | 11 +++-------
> utils/mountd/mountd.h | 2 +-
> utils/mountd/mountd.man | 8 -------
> utils/mountd/v4root.c | 6 +++--
> 9 files changed, 84 insertions(+), 57 deletions(-)
>
> --
> Signature
next prev parent reply other threads:[~2016-07-29 19:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 5:03 [PATCH 0/7] Assorted mount/mountd nfs-utils patches - V2 NeilBrown
2016-07-29 5:03 ` [PATCH 7/7] mountd: fail nfsd.export lookup for path to unmounted exportpoint NeilBrown
2016-07-29 19:04 ` J. Bruce Fields
2016-07-29 5:03 ` [PATCH 4/7] mount: use a public address for IPv6 callback NeilBrown
2016-07-29 5:03 ` [PATCH 1/7] nfs.man: clarify effect of 'retry' option NeilBrown
2016-07-29 5:03 ` [PATCH 5/7] mount: fix memory leak in v4root_add_parents NeilBrown
2016-07-29 5:03 ` [PATCH 3/7] mount: don't treat temporary name resolution failure as permanent NeilBrown
2016-07-29 5:03 ` [PATCH 6/7] mountd: allow alternate ttl to be specified for dump_to_cache NeilBrown
2016-08-03 17:31 ` Steve Dickson
2016-08-03 17:59 ` Steve Dickson
2016-07-29 5:03 ` [PATCH 2/7] mountd: remove the --exports-file option NeilBrown
2016-07-29 19:05 ` J. Bruce Fields [this message]
2016-08-04 11:50 ` [PATCH 0/7] Assorted mount/mountd nfs-utils patches - V2 Steve Dickson
2016-08-04 12:06 ` NeilBrown
2016-08-04 17:29 ` Steve Dickson
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=20160729190541.GC7964@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).