linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Chris Siebenmann <cks.nfs01@cs.toronto.edu>, linux-nfs@vger.kernel.org
Cc: cks.nfs01@cs.toronto.edu
Subject: Re: Manual page bug: two inaccuracies in nfsd(7)
Date: Mon, 13 Feb 2017 15:46:10 +1100	[thread overview]
Message-ID: <87tw7y4s19.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20170210185410.7425E5A06F8@apps1.cs.toronto.edu>

[-- Attachment #1: Type: text/plain, Size: 2439 bytes --]

On Fri, Feb 10 2017, Chris Siebenmann wrote:

>  I was recently reading this manual page as part of exploring running
> an NFS server on Ubuntu 16.04 (with Ubuntu's kernel '4.4.0') and found
> two inaccuracies with the current state of the kernel (or at least how
> it looks to me based on both experimentation and code).
>
>  First, there is no /proc/net/rpc/auth.domain directory and cache any
> more. This was removed from the kernel in 2006 (in commit efc36aa5608f),
> so I think it should be safe to remove from current versions of the
> manpage.

I agree.

>
>  Second, the manpage says about the 'flush' files to be found in eg
> /proc/net/rpc/auth.unix.ip:
>
> 	When a number of seconds since epoch (1 Jan 1970) is written to
> 	this file, all entries in the cache that were last updated before
> 	that file become invalidated and will be flushed out. Writing
> 	1 will flush everything. [...]
>
> The bit about 'writing 1 will flush everything' does not appear to be
> accurate.

I was never accurate.  I vaguely remember writing it.  I must have been
confused.

Would you be able to create a patch which fixes these issues, and post
it, with a signed-off-by ?

Thanks,
NeilBrown



>            Experimentally, writing 1 does not work (it flushes nothing),
> and in the current kernel code there is no special handling for a write of
> '1' to the "flush" files in net/sunrpc/cache.c's write_flush() function,
> which I believe is where this is implemented. Based on the implementation,
> the only way to flush everything is to write a time in the future to
> "flush".
>
>  Based on looking at the kernel logs and code diffs, this may have
> changed in commit 778620364ef5, 'sunrpc/cache: make cache flushing more
> reliable', which gitk tells me came between v4.3-rc3 and v4.4-rc1 (it
> was made in October 2015). The commit description definitely talks about
> changing how cache expiry works, and it touches write_flush() et al in
> various ways. This may call for a kernel change to make it work again,
> but even if so I would suggest that the manpage be updated to reflect
> that writing 1 doesn't work in a range of kernel versions (some of which
> will be in the field for years to come, eg Ubuntu 16.04 LTS).
>
> 	- cks
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-02-13  4:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 18:54 Manual page bug: two inaccuracies in nfsd(7) Chris Siebenmann
2017-02-13  4:46 ` NeilBrown [this message]
2017-02-23 16:46   ` Chris Siebenmann
2017-03-02 23:28     ` NeilBrown
2017-03-14 14:42       ` 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=87tw7y4s19.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=cks.nfs01@cs.toronto.edu \
    --cc=linux-nfs@vger.kernel.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 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).