From: Chuck Lever <chuck.lever@oracle.com>
To: anna.schumaker@netapp.com
Cc: linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] xprtrdma device removal bug fixes
Date: Mon, 02 Dec 2019 11:28:33 -0500 [thread overview]
Message-ID: <20191202162242.4115.94732.stgit@manet.1015granger.net> (raw)
Hi Anna-
Here are two bug fixes related to DEVICE_REMOVAL support in the
RPC/RDMA client. Can these go in 5.5-rc ?
Both of these deserve a stable tag, IMHO, as does 572c4b40a394
("xprtrdma: Fix MR list handling") which I've already sent as
part of for-5.5.
There's one remaining crasher that I hit when removing a device
while there are active NFS mounts. I should have a fix for that
one soon.
---
Chuck Lever (2):
xprtrdma: Fix create_qp crash on device unload
xprtrdma: Fix completion wait during device removal
net/sunrpc/xprtrdma/verbs.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
Chuck Lever
next reply other threads:[~2019-12-02 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 16:28 Chuck Lever [this message]
2019-12-02 16:28 ` [PATCH 1/2] xprtrdma: Fix create_qp crash on device unload Chuck Lever
2019-12-02 16:28 ` [PATCH 2/2] xprtrdma: Fix completion wait during device removal Chuck Lever
2019-12-02 16:40 ` Chuck Lever
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=20191202162242.4115.94732.stgit@manet.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@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).