linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [GIT PULL] nfsd changes for 5.4
Date: Fri, 27 Sep 2019 15:44:02 -0700	[thread overview]
Message-ID: <CAHk-=wj_bMxjz_T9Oa62Uyp8tKnKomtHKV9HTnuvMxrdwuTPOg@mail.gmail.com> (raw)
In-Reply-To: <20190927200838.GA2618@fieldses.org>

On Fri, Sep 27, 2019 at 1:08 PM J. Bruce Fields <bfields@fieldses.org> wrote:
>
> Please pull nfsd changes from:
>
>   git://linux-nfs.org/~bfields/linux.git tags/nfsd-5.4

Hmm. I styarted to pull, but then realized that the description
doesn't match the content at all.

You say:

> Highlights:
>
>         - add a new knfsd file cache, so that we don't have to open and
>           close on each (NFSv2/v3) READ or WRITE.  This can speed up
>           read and write in some cases.  It also replaces our readahead
>           cache.
>         - Prevent silent data loss on write errors, by treating write
>           errors like server reboots for the purposes of write caching,
>           thus forcing clients to resend their writes.
>         - Tweak the code that allocates sessions to be more forgiving,
>           so that NFSv4.1 mounts are less likely to hang when a server
>           already has a lot of clients.
>         - Eliminate an arbitrary limit on NFSv4 ACL sizes; they should
>           now be limited only by the backend filesystem and the
>           maximum RPC size.
>         - Allow the server to enforce use of the correct kerberos
>           credentials when a client reclaims state after a reboot.
>
> And some miscellaneous smaller bugfixes and cleanup.

But then the actual code is just one single small commit:

> Dave Wysochanski (1):
>       SUNRPC: Track writers of the 'channel' file to improve cache_listeners_exist

which doesn't actually match any of the things your description says
should be there.

So I undid my pull - either the description is completely wrong, or
you tagged the wrong commit.

Please double-check,

             Linus

  reply	other threads:[~2019-09-27 22:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27 20:08 [GIT PULL] nfsd changes for 5.4 J. Bruce Fields
2019-09-27 22:44 ` Linus Torvalds [this message]
2019-09-27 23:55   ` J. Bruce Fields
2019-09-28  1:15     ` pr-tracker-bot
2019-09-28  1:15 ` pr-tracker-bot

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='CAHk-=wj_bMxjz_T9Oa62Uyp8tKnKomtHKV9HTnuvMxrdwuTPOg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).