All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Malavali, Giridhar" <Giridhar.Malavali@cavium.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Bart Van Assche <bart.vanassche@sandisk.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"Madhani, Himanshu" <Himanshu.Madhani@cavium.com>,
	"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>
Subject: Re: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.
Date: Thu, 9 Mar 2017 21:08:49 +0000	[thread overview]
Message-ID: <D4E703FD.8B202%giridhar.malavali@cavium.com> (raw)
In-Reply-To: <1489030953.10589.40.camel@haakon3.risingtidesystems.com>



On 3/8/17, 7:42 PM, "Nicholas A. Bellinger" <nab@linux-iscsi.org> wrote:

>Hi Giri,
>
>On Wed, 2017-03-08 at 18:30 +0000, Malavali, Giridhar wrote:
>> 
>> On 3/8/17, 7:20 AM, "Bart Van Assche" <Bart.VanAssche@sandisk.com>
>>wrote:
>> 
>> >On Tue, 2017-03-07 at 23:34 -0800, Nicholas A. Bellinger wrote:
>> >> Btw, the regression reported here in v2:
>> >> 
>> >> http://www.spinics.net/lists/target-devel/msg14348.html
>> >> 
>> >> is completely different from what you've reported here.
>> >
>> >The call traces differ but the root cause is probably the same.
>> >
>> >> It would be useful to explain how you reproduced this, instead of
>>just
>> >> posting backtrace with zero context..?
>> >> 
>> >> Can we at least identify which patch in this series is causing
>>this..?
>> >> 
>> >> Also, I assume you are running this on stock v4.11-rc1 with only this
>> >> qla2xxx series applied, and not all of your other stuff, right..?
>> >
>> >The test I ran against v4.11-rc1 + this patch series is to start LIO
>>on a
>> >system equipped with two back-to-back connected QLogic FC HBAs (no
>>switch
>> >inbetween), to load the tcm_qla2xxx driver, to configure LUNs and to
>>wait
>> >until the SCSI stack reports that these LUNs have appeared. What I see
>>in
>> >the lsscsi output with both v2 and v3 of this patch series is that
>>these
>> >LUNs appear briefly and then disappear and that a little bit later the
>> >kernel reports that a hang occurred. Without this patch series the LUNs
>> >are
>> >detected and do not disappear automatically and no hang is reported. I
>> >think the next step is that Cavium verifies whether they can reproduce
>> >this
>> >behavior and if they can reproduce it to run a bisect. BTW, since there
>> >are
>> >login-related patches in this series I wouldn't be surprised if one of
>> >these
>> >patches introduced the regression.
>> 
>> We generally go through switch. We will try to reproduce with back to
>>back
>> and bisect the patches.
>> 
>
>Just a heads up given this series mixes bug-fixes with a few other
>miscellaneous improvements, I'd like to get it pushed to Linus with the
>next round of patches no later than -rc3.
>
>If it's beyond -rc3, then the bug-fixes will need to be split out for
>v4.11-rc separate from the other improvements.

Thanks for the heads-up. We are working on Bart reported issue. We are
able to recreate this internally.
We should be able to wrap it up in next few days and send the final
patches. I don¹t think anything else is outstanding.

‹ Giri

>

  reply	other threads:[~2017-03-09 21:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24 21:37 [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 01/14] qla2xxx: Fix delayed response to command for loop mode/direct connect Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 02/14] qla2xxx: Allow relogin to proceed if remote login did not finish Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 03/14] qla2xxx: Allow vref count to timeout on vport delete Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 04/14] qla2xxx: Use IOCB interface to submit non-critical MBX Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 05/14] qla2xxx: Add DebugFS node to display Port Database Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 06/14] qla2xxx: Improve T10-DIF/PI handling in driver Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 07/14] qla2xxx: Export DIF stats via debugfs Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 08/14] qla2xxx: Change scsi host lookup method Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 09/14] qla2xxx: Fix memory leak for abts processing Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 10/14] qla2xxx: Fix request queue corruption Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 11/14] qla2xxx: Fix inadequate lock protection for ABTS Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 12/14] qla2xxx: Add async new target notification Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 13/14] qla2xxx: Fix sess_lock & hardware_lock lock order problem Himanshu Madhani
2017-02-24 21:37 ` [PATCH v3 14/14] qla2xxx: Update driver version to 9.00.00.00-k Himanshu Madhani
2017-02-28 22:00 ` [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target Madhani, Himanshu
2017-02-28 22:09   ` Bart Van Assche
2017-02-28 22:13     ` Madhani, Himanshu
2017-03-02  7:24 ` Nicholas A. Bellinger
2017-03-06  0:43 ` Bart Van Assche
2017-03-06  5:05   ` Madhani, Himanshu
2017-03-08  7:34   ` Nicholas A. Bellinger
2017-03-08 15:20     ` Bart Van Assche
2017-03-08 18:30       ` Malavali, Giridhar
2017-03-09  3:42         ` Nicholas A. Bellinger
2017-03-09 21:08           ` Malavali, Giridhar [this message]
2017-03-09  3:38       ` Nicholas A. Bellinger

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=D4E703FD.8B202%giridhar.malavali@cavium.com \
    --to=giridhar.malavali@cavium.com \
    --cc=Himanshu.Madhani@cavium.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --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.