From: Chuck Lever <chuck.lever@oracle.com>
To: anna.schumaker@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] Fixes for v5.4
Date: Fri, 03 Jan 2020 11:52:06 -0500 [thread overview]
Message-ID: <157807026361.3637.2531475820164100233.stgit@morisot.1015granger.net> (raw)
Hi Anna-
I haven't seen these three go into 5.4 stable yet. Can they be
pushed soon?
---
Chuck Lever (3):
xprtrdma: Fix create_qp crash on device unload
xprtrdma: Fix completion wait during device removal
xprtrdma: Fix oops in Receive handler after device removal
net/sunrpc/xprtrdma/verbs.c | 29 ++++++++++++++++++++++-------
net/sunrpc/xprtrdma/xprt_rdma.h | 2 ++
2 files changed, 24 insertions(+), 7 deletions(-)
--
Chuck Lever
next reply other threads:[~2020-01-03 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 16:52 Chuck Lever [this message]
2020-01-03 16:52 ` [PATCH 1/3] xprtrdma: Fix create_qp crash on device unload Chuck Lever
2020-01-03 16:52 ` [PATCH 2/3] xprtrdma: Fix completion wait during device removal Chuck Lever
2020-01-03 16:52 ` [PATCH 3/3] xprtrdma: Fix oops in Receive handler after " 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=157807026361.3637.2531475820164100233.stgit@morisot.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=anna.schumaker@netapp.com \
--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).