From: Bart Van Assche <bvanassche@acm.org>
To: "Marciniszyn, Mike" <mike.marciniszyn@intel.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: "target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
Dakshaja Uppalapati <dakshaja@chelsio.com>,
Sagi Grimberg <sagi@grimberg.me>,
Rahul Kundu <rahul.kundu@chelsio.com>,
"'linux-rdma@vger.kernel.org'" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH 1/2] Revert "RDMA/isert: Fix a recently introduced regression related to logout"
Date: Fri, 14 Feb 2020 11:07:33 -0800 [thread overview]
Message-ID: <0763a928-27f4-d6cf-fc54-128ddaf2f47f@acm.org> (raw)
In-Reply-To: <MWHPR1101MB227101D7C2DFEB8ABACD0FCB86150@MWHPR1101MB2271.namprd11.prod.outlook.com>
On 2/14/20 6:28 AM, Marciniszyn, Mike wrote:
>>
>> [PATCH 0/2] Revert two recent iSCSI / iSER patches
>>
>
> Bart,
>
> This will mean we will again see failures in our internal iSer testing.
>
> What is the status of a final fix?
>
> If you have something to try, I would be glad to test...
Hi Mike,
Please take another look at this patch series. No new regressions should
be introduced except if someone runs a bisect that lands in the middle
of this patch series. Patch 1/2 reintroduces a regression but patches
1/2 and 2/2 combined should restore iSER to the state of that driver in
kernel v5.4.
Thanks,
Bart.
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <bvanassche@acm.org>
To: "Marciniszyn, Mike" <mike.marciniszyn@intel.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: "target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
Dakshaja Uppalapati <dakshaja@chelsio.com>,
Sagi Grimberg <sagi@grimberg.me>,
Rahul Kundu <rahul.kundu@chelsio.com>,
"'linux-rdma@vger.kernel.org'" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH 1/2] Revert "RDMA/isert: Fix a recently introduced regression related to logout"
Date: Fri, 14 Feb 2020 19:07:33 +0000 [thread overview]
Message-ID: <0763a928-27f4-d6cf-fc54-128ddaf2f47f@acm.org> (raw)
In-Reply-To: <MWHPR1101MB227101D7C2DFEB8ABACD0FCB86150@MWHPR1101MB2271.namprd11.prod.outlook.com>
On 2/14/20 6:28 AM, Marciniszyn, Mike wrote:
>>
>> [PATCH 0/2] Revert two recent iSCSI / iSER patches
>>
>
> Bart,
>
> This will mean we will again see failures in our internal iSer testing.
>
> What is the status of a final fix?
>
> If you have something to try, I would be glad to test...
Hi Mike,
Please take another look at this patch series. No new regressions should
be introduced except if someone runs a bisect that lands in the middle
of this patch series. Patch 1/2 reintroduces a regression but patches
1/2 and 2/2 combined should restore iSER to the state of that driver in
kernel v5.4.
Thanks,
Bart.
next prev parent reply other threads:[~2020-02-14 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 5:08 [PATCH 1/2] Revert "RDMA/isert: Fix a recently introduced regression related to logout" Bart Van Assche
2020-02-13 5:25 ` Bart Van Assche
2020-02-14 14:28 ` Marciniszyn, Mike
2020-02-14 14:28 ` Marciniszyn, Mike
2020-02-14 19:07 ` Bart Van Assche [this message]
2020-02-14 19:07 ` Bart Van Assche
2020-02-14 22:14 ` Martin K. Petersen
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=0763a928-27f4-d6cf-fc54-128ddaf2f47f@acm.org \
--to=bvanassche@acm.org \
--cc=dakshaja@chelsio.com \
--cc=linux-rdma@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mike.marciniszyn@intel.com \
--cc=rahul.kundu@chelsio.com \
--cc=sagi@grimberg.me \
--cc=target-devel@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.