From: "Raju Rangoju" <rajur@chelsio.com>
To: Christoph Hellwig <hch@lst.de>,
SWise OGC <swise@opengridcomputing.com>,
Sagi Grimberg <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "maxg@mellanox.com" <maxg@mellanox.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH v3] nvmet-rdma: fix null dereference under heavy load
Date: Fri, 18 Jan 2019 07:37:54 +0000 [thread overview]
Message-ID: <MWHPR1201MB0080D99508074185EB018406BC9C0@MWHPR1201MB0080.namprd12.prod.outlook.com> (raw)
In-Reply-To: <3c2a416a-89c0-d63c-aedf-4f871dc26fc8@opengridcomputing.com>
Hi Christoph,
In case you missed, could you please pull this patch ?
-Raju
-----Original Message-----
From: Steve Wise <swise@opengridcomputing.com>
Sent: 07 January 2019 21:29
To: Sagi Grimberg <sagi@grimberg.me>; Raju Rangoju <rajur@chelsio.com>; linux-nvme@lists.infradead.org
Cc: maxg@mellanox.com; stable@vger.kernel.org
Subject: Re: [PATCH v3] nvmet-rdma: fix null dereference under heavy load
On 1/3/2019 5:13 PM, Sagi Grimberg wrote:
> Wonder how the original fix got a tested-by...
>
> Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
That was my bad. But the testers said they couldn't reproduce the issue, so I assumed that meant it was fixed. I guess they weren't stressing it enough.
Steve.
next prev parent reply other threads:[~2019-01-18 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 17:35 [PATCH v3] nvmet-rdma: fix null dereference under heavy load Raju Rangoju
2019-01-03 23:13 ` Sagi Grimberg
2019-01-07 15:59 ` Steve Wise
2019-01-18 7:37 ` Raju Rangoju [this message]
2019-01-19 13:34 ` Christoph Hellwig
2019-01-21 9:10 ` Sagi Grimberg
2019-01-21 13:07 ` Max Gurtovoy
2019-01-21 15:46 ` Steve Wise
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=MWHPR1201MB0080D99508074185EB018406BC9C0@MWHPR1201MB0080.namprd12.prod.outlook.com \
--to=rajur@chelsio.com \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=maxg@mellanox.com \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.org \
--cc=swise@opengridcomputing.com \
/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).