From: Max Gurtovoy <maxg@mellanox.com>
To: Christoph Hellwig <hch@lst.de>
Cc: <jgg@mellanox.com>, <keith.busch@intel.com>,
<linux-nvme@lists.infradead.org>, <sagi@grimberg.me>,
<leon@kernel.org>, <oren@mellanox.com>, <idanb@mellanox.com>,
<vladimirk@mellanox.com>, <stable@vger.kernel.org>,
<martin.petersen@oracle.com>
Subject: Re: [PATCH 01/17] IB/isert: fix T10-pi check mask setting
Date: Mon, 28 May 2018 15:04:38 +0300 [thread overview]
Message-ID: <99191c8c-b03e-f40d-ffd9-a73e01d0ae2a@mellanox.com> (raw)
In-Reply-To: <20180528120359.GA13368@lst.de>
Hi Martin/Jason,
can you please coordinate on taking this fix through your PR (RDMA or
SCSi) ?
On 5/28/2018 3:03 PM, Christoph Hellwig wrote:
> On Mon, May 28, 2018 at 02:54:48PM +0300, Max Gurtovoy wrote:
>>
>>
>> On 5/28/2018 10:21 AM, Christoph Hellwig wrote:
>>> On Sun, May 27, 2018 at 06:50:06PM +0300, Max Gurtovoy wrote:
>>>> A copy/paste bug (probably) caused setting of an app_tag check mask
>>>> in case where a ref_tag check was needed.
>>>>
>>>> Fixes: 38a2d0d429f1 ("IB/isert: convert to the generic RDMA READ/WRITE API")
>>>> Fixes: 9e961ae73c2c ("IB/isert: Support T10-PI protected transactions")
>>>> Cc: stable@vger.kernel.org
>>>> Signed-off-by: Max Gurtovoy <maxg@mellanox.com>
>>>
>>> Looks good, and should probably got into the scsi tree ASAP.
>>
>> Yes, there are few patches that can be pushed "as is".
>>
>> Should it go through Nicholas PR ?
>
> Nic has been non-responsive for a while and Martin has queued up
> target fixes when needed.
>
next prev parent reply other threads:[~2018-05-28 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1527436222-15494-1-git-send-email-maxg@mellanox.com>
2018-05-27 15:50 ` [PATCH 01/17] IB/isert: fix T10-pi check mask setting Max Gurtovoy
2018-05-28 7:21 ` Christoph Hellwig
2018-05-28 11:54 ` Max Gurtovoy
2018-05-28 12:03 ` Christoph Hellwig
2018-05-28 12:04 ` Max Gurtovoy [this message]
2018-05-28 16:33 ` Jason Gunthorpe
2018-05-29 3:01 ` Martin K. Petersen
2018-05-29 12:08 ` Max Gurtovoy
2018-05-29 19:23 ` Jason Gunthorpe
2018-05-29 22:11 ` Martin K. Petersen
2018-05-29 22:19 ` Jason Gunthorpe
2018-05-29 22:41 ` Martin K. Petersen
2018-05-30 8:07 ` Max Gurtovoy
2018-05-30 15:30 ` Jason Gunthorpe
2018-05-30 21:47 ` Sagi Grimberg
2018-05-30 21:49 ` Sagi Grimberg
[not found] <1527191377-11513-1-git-send-email-maxg@mellanox.com>
2018-05-24 19:49 ` Max Gurtovoy
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=99191c8c-b03e-f40d-ffd9-a73e01d0ae2a@mellanox.com \
--to=maxg@mellanox.com \
--cc=hch@lst.de \
--cc=idanb@mellanox.com \
--cc=jgg@mellanox.com \
--cc=keith.busch@intel.com \
--cc=leon@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=oren@mellanox.com \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.org \
--cc=vladimirk@mellanox.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).