From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [GIT PULL] another nfsd bugfix for 4.9
Date: Fri, 18 Nov 2016 15:22:02 -0500 [thread overview]
Message-ID: <20161118202202.GE5424@fieldses.org> (raw)
In-Reply-To: <20161118191008.GB5424@fieldses.org>
Also, this commit (ea08e39230e8 "sunrpc: svc_age_temp_xprts_now should
not call setsockopt non-tcp transports") fixes a bug going back to 4.5,
so should have been tagged for stable.
--b.
On Fri, Nov 18, 2016 at 02:10:08PM -0500, bfields wrote:
> Please pull:
>
> git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.9-2
>
> Just one fix for an NFS/RDMA crash.
>
> --b.
>
> Scott Mayhew (1):
> sunrpc: svc_age_temp_xprts_now should not call setsockopt non-tcp transports
>
> include/linux/sunrpc/svc_xprt.h | 1 +
> net/sunrpc/svc_xprt.c | 11 +----------
> net/sunrpc/svcsock.c | 21 +++++++++++++++++++++
> net/sunrpc/xprtrdma/svc_rdma_transport.c | 6 ++++++
> 4 files changed, 29 insertions(+), 10 deletions(-)
parent reply other threads:[~2016-11-18 20:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20161118191008.GB5424@fieldses.org>]
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=20161118202202.GE5424@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).