From: Greg KH <gregkh@linuxfoundation.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Timo Rothenpieler <timo@rothenpieler.org>, stable@vger.kernel.org
Subject: Re: Backport request: nfsd: Fix NFSv4 READ on RDMA when using readv
Date: Mon, 10 Aug 2020 16:15:18 +0200 [thread overview]
Message-ID: <20200810141518.GA3758520@kroah.com> (raw)
In-Reply-To: <22C4A9C2-5986-447C-B91E-DC2F9653A7E9@oracle.com>
On Mon, Aug 10, 2020 at 09:57:56AM -0400, Chuck Lever wrote:
> Hi Greg-
>
> > On Aug 10, 2020, at 9:52 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Aug 04, 2020 at 10:47:26PM +0200, Timo Rothenpieler wrote:
> >> Sorry if this is not the right approach to this, but I'd like to request a
> >> backport of 412055398b9e67e07347a936fc4a6adddabe9cf4, "nfsd: Fix NFSv4 READ
> >> on RDMA when using readv" to Linux 5.4.
> >>
> >> The patch applies cleanly and fixes a rare but severe issue with NFS over
> >> RDMA, which I just spent several days tracking down to that patch, with
> >> major help from linux-nfs/rdma.
> >>
> >> I have right now manually applied it to my 5.4 Kernel and can confirm it
> >> fixes the issue.
> >
> > It's good to cc: the developers/maintainers of the patch you are asking
> > about, to see if they object or not.
> >
> > Chuck, any objection for the above patch being added to 5.4 and maybe
> > 4.19?
>
> Since Timo applied it to 5.4 and tested it, I have no objection there.
>
> v4.19 suffers from the same bug, but I don't have reports of anyone
> having tried 4120553 on that kernel. I would say wait on that one until
> someone can state that it works without regression.
Ok, sounds good, now queued up for 5.4.y, thanks!
greg k-h
prev parent reply other threads:[~2020-08-10 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 20:47 Backport request: nfsd: Fix NFSv4 READ on RDMA when using readv Timo Rothenpieler
2020-08-10 13:52 ` Greg KH
2020-08-10 13:57 ` Chuck Lever
2020-08-10 14:15 ` Greg KH [this message]
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=20200810141518.GA3758520@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chuck.lever@oracle.com \
--cc=stable@vger.kernel.org \
--cc=timo@rothenpieler.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