From: Greg KH <greg@kroah.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: stable@vger.kernel.org, Vasco Steinmetz <linux@kyberraum.net>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [stable 4.8] xprtrdma: Fix DMAR failure in frwr_op_map() after reconnect
Date: Thu, 17 Nov 2016 08:15:23 +0100 [thread overview]
Message-ID: <20161117071523.GA5435@kroah.com> (raw)
In-Reply-To: <480AB524-3381-4699-B6E3-1D4D16FF843C@oracle.com>
On Wed, Nov 16, 2016 at 03:50:47PM -0500, Chuck Lever wrote:
> Please cherry-pick this commit for v4.8 stable:
>
> commit 62bdf94a2049822ef8c6d4b0e83cd9c3a1663ab4
> Author: Chuck Lever <chuck.lever@oracle.com>
> AuthorDate: Mon Nov 7 16:16:24 2016 -0500
> Commit: Anna Schumaker <Anna.Schumaker@Netapp.com>
> CommitDate: Thu Nov 10 11:04:54 2016 -0500
>
> xprtrdma: Fix DMAR failure in frwr_op_map() after reconnect
>
> This commit is needed to prevent DMAR errors during a spurious
> RDMA connection close. Problem reported by Vasco Steinmetz.
>
> To apply 62bdf94a cleanly to v4.8.7, please first apply this
> one-line clean-up commit:
>
> commit 5690a22d8612e1788b48b4ea53c59868589cd2db
> Author: Daniel Wagner <daniel.wagner@bmw-carit.de>
> AuthorDate: Fri Sep 23 10:41:57 2016 +0200
> Commit: Anna Schumaker <Anna.Schumaker@Netapp.com>
> CommitDate: Fri Sep 23 09:48:24 2016 -0400
>
> xprtrdma: use complete() instead complete_all()
>
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2016-11-17 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 20:50 [stable 4.8] xprtrdma: Fix DMAR failure in frwr_op_map() after reconnect Chuck Lever
2016-11-17 7: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=20161117071523.GA5435@kroah.com \
--to=greg@kroah.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux@kyberraum.net \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.