Re: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Malavali, Giridhar]

On 3/8/17, 7:42 PM, "Nicholas A. Bellinger"  wrote:

>Hi Giri,
>
>On Wed, 2017-03-08 at 18:30 +, Malavali, Giridhar wrote:
>> 
>> On 3/8/17, 7:20 AM, "Bart Van Assche" 
>>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

>

Re: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Nicholas A. Bellinger]

Hi Giri,

On Wed, 2017-03-08 at 18:30 +, Malavali, Giridhar wrote:
> 
> On 3/8/17, 7:20 AM, "Bart Van Assche"  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.

Re: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Nicholas A. Bellinger]

On Wed, 2017-03-08 at 15:20 +, Bart Van Assche 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.
> 

Good.  Thanks for confirming it's with a PTP setup, and atop stock
v4.11-rc1 with this series.

Re: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Malavali, Giridhar]

On 3/8/17, 7:20 AM, "Bart Van Assche"  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.

‹ Giri


>
>Bart.

Re: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Bart Van Assche]

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.

Bart.

Re: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Nicholas A. Bellinger]

On Mon, 2017-03-06 at 00:43 +, Bart Van Assche wrote:
> On Fri, 2017-02-24 at 13:37 -0800, Himanshu Madhani wrote:
> > Please consider this series for inclusion in target-pending.
> 
> Hello Himanshu,
> 
> I applied this patch series on top of kernel v4.11-rc1 and installed it on
> a test system. Unfortunately the regression I reported one month ago against
> v2 of this patch series still occurs with v3 of this patch series:

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.

> 
> INFO: task kworker/2:1:71 blocked for more than 120 seconds.
>   Not tainted 4.11.0-rc1-dbg+ #1
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> kworker/2:1 D071  2 0x
> Workqueue: events qlt_free_session_done [qla2xxx]
> Call Trace:
>  __schedule+0x1ef/0xa70
>  schedule+0x40/0x90
>  schedule_timeout+0x258/0x4a0
>  wait_for_completion+0x108/0x170
>  target_wait_for_sess_cmds+0x56/0x1b0 [target_core_mod]
>  tcm_qla2xxx_free_session+0x45/0x90 [tcm_qla2xxx]
>  qlt_free_session_done+0x44a/0x550 [qla2xxx]
>  process_one_work+0x20d/0x6c0
>  worker_thread+0x4e/0x4a0
>  kthread+0x10c/0x140
>  ret_from_fork+0x31/0x40
> 

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..?

RE: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Madhani, Himanshu]

> -Original Message-
> From: Bart Van Assche [mailto:bart.vanass...@sandisk.com]
> Sent: Sunday, March 5, 2017 4:43 PM
> To: Madhani, Himanshu <himanshu.madh...@cavium.com>; target-
> de...@vger.kernel.org; n...@linux-iscsi.org
> Cc: linux-scsi@vger.kernel.org; Malavali, Giridhar
> <giridhar.malav...@cavium.com>
> Subject: Re: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.
> 
> On Fri, 2017-02-24 at 13:37 -0800, Himanshu Madhani wrote:
> > Please consider this series for inclusion in target-pending.
> 
> Hello Himanshu,
> 
> I applied this patch series on top of kernel v4.11-rc1 and installed it on a 
> test
> system. Unfortunately the regression I reported one month ago against
> v2 of this patch series still occurs with v3 of this patch series:
> 
> INFO: task kworker/2:1:71 blocked for more than 120 seconds.
>   Not tainted 4.11.0-rc1-dbg+ #1
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> kworker/2:1 D071  2 0x
> Workqueue: events qlt_free_session_done [qla2xxx] Call Trace:
>  __schedule+0x1ef/0xa70
>  schedule+0x40/0x90
>  schedule_timeout+0x258/0x4a0
>  wait_for_completion+0x108/0x170
>  target_wait_for_sess_cmds+0x56/0x1b0 [target_core_mod]
>  tcm_qla2xxx_free_session+0x45/0x90 [tcm_qla2xxx]
>  qlt_free_session_done+0x44a/0x550 [qla2xxx]
>  process_one_work+0x20d/0x6c0
>  worker_thread+0x4e/0x4a0
>  kthread+0x10c/0x140
>  ret_from_fork+0x31/0x40
> 
> Bart

We'll take a look.

Re: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Bart Van Assche]

On Fri, 2017-02-24 at 13:37 -0800, Himanshu Madhani wrote:
> Please consider this series for inclusion in target-pending.

Hello Himanshu,

I applied this patch series on top of kernel v4.11-rc1 and installed it on
a test system. Unfortunately the regression I reported one month ago against
v2 of this patch series still occurs with v3 of this patch series:

INFO: task kworker/2:1:71 blocked for more than 120 seconds.
  Not tainted 4.11.0-rc1-dbg+ #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/2:1 D071  2 0x
Workqueue: events qlt_free_session_done [qla2xxx]
Call Trace:
 __schedule+0x1ef/0xa70
 schedule+0x40/0x90
 schedule_timeout+0x258/0x4a0
 wait_for_completion+0x108/0x170
 target_wait_for_sess_cmds+0x56/0x1b0 [target_core_mod]
 tcm_qla2xxx_free_session+0x45/0x90 [tcm_qla2xxx]
 qlt_free_session_done+0x44a/0x550 [qla2xxx]
 process_one_work+0x20d/0x6c0
 worker_thread+0x4e/0x4a0
 kthread+0x10c/0x140
 ret_from_fork+0x31/0x40

Bart.

Re: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Nicholas A. Bellinger]

Hi Himanshu & Co,

On Fri, 2017-02-24 at 13:37 -0800, Himanshu Madhani wrote:
> Hi Nic,
> 
> Please consider this series for inclusion in target-pending.
> 

This is a little late to include for v4.11-rc1, but considering the
number of bug-fixes I'm OK to merge it post -rc1.

> This series contains following changes.
> 
> o Fix for the deadlock because of inconsistent lock usage reported by you.
> o Added patch to submit non-critical MBX command via IOCB path.
> o Improved T10-DIF/PI handling with target stack.
> o Changed scsi host lookup method.
> o Some minor bug fixes.
> 
> Changes from v2 --> v3
> 
> o Updated patch to use waitq instead of while loop for waiting.
> o Removed duplication of Target stack definitations for T10-DIF/PI.
> o In addition, addressed review comments from Bart & Christoph.
> 
> Changes from v1 -> v2
> 
> o Rebased series based on scsi-target-for-v4.11 branch.
> 
> Please apply to target-pending.
> 
> Thanks,
> Himanshu 
> 
> Anil Gurumurthy (1):
>   qla2xxx: Export DIF stats via debugfs
> 
> Himanshu Madhani (2):
>   qla2xxx: Add DebugFS node to display Port Database
>   qla2xxx: Update driver version to 9.00.00.00-k
> 
> Joe Carnuccio (1):
>   qla2xxx: Allow vref count to timeout on vport delete.
> 
> Quinn Tran (10):
>   qla2xxx: Fix delayed response to command for loop mode/direct connect.
>   qla2xxx: Allow relogin to proceed if remote login did not finish
>   qla2xxx: Use IOCB interface to submit non-critical MBX.
>   qla2xxx: Improve T10-DIF/PI handling in driver.
>   qla2xxx: Change scsi host lookup method.
>   qla2xxx: Fix memory leak for abts processing
>   qla2xxx: Fix request queue corruption.
>   qla2xxx: Fix inadequate lock protection for ABTS.
>   qla2xxx: Add async new target notification
>   qla2xxx: Fix sess_lock & hardware_lock lock order problem.
> 
>  drivers/scsi/qla2xxx/Kconfig   |   1 +
>  drivers/scsi/qla2xxx/qla_attr.c|   4 +-
>  drivers/scsi/qla2xxx/qla_dbg.h |   1 +
>  drivers/scsi/qla2xxx/qla_def.h |  46 ++-
>  drivers/scsi/qla2xxx/qla_dfs.c | 115 +-
>  drivers/scsi/qla2xxx/qla_gbl.h |  12 +-
>  drivers/scsi/qla2xxx/qla_init.c|  85 ++---
>  drivers/scsi/qla2xxx/qla_isr.c |  41 ++-
>  drivers/scsi/qla2xxx/qla_mbx.c | 304 ++--
>  drivers/scsi/qla2xxx/qla_mid.c |  14 +-
>  drivers/scsi/qla2xxx/qla_os.c  |  24 +-
>  drivers/scsi/qla2xxx/qla_target.c  | 729 
> +++--
>  drivers/scsi/qla2xxx/qla_target.h  |  36 +-
>  drivers/scsi/qla2xxx/qla_version.h |   6 +-
>  drivers/scsi/qla2xxx/tcm_qla2xxx.c |  49 ++-
>  15 files changed, 1049 insertions(+), 418 deletions(-)
> 

RE: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Madhani, Himanshu]

> -Original Message-
> From: Bart Van Assche [mailto:bart.vanass...@sandisk.com]
> Sent: Tuesday, February 28, 2017 2:10 PM
> To: Madhani, Himanshu <himanshu.madh...@cavium.com>; target-
> de...@vger.kernel.org; n...@linux-iscsi.org
> Cc: linux-scsi@vger.kernel.org; Malavali, Giridhar
> <giridhar.malav...@cavium.com>
> Subject: Re: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.
> 
> On Tue, 2017-02-28 at 22:00 +, Madhani, Himanshu wrote:
> > Can we get some review comments for this series.
> 
> Hello Himanshu,
> 
> The merge window opened one week ago and is still open. Anyone who
> contributes to the Linux kernel should know that patches should not be
> posted during the merge window because it's a busy time for most kernel
> contributors. Additionally, no feedback should be expected during the merge
> window for patches that are not bug fixes for changes that went in during
> the merge window. Anyway, I'll have a look at these patches as soon as I
> have the time.
> 
> Bart.

Sorry for the ignorance. I did not realize merge window was open. 

Thanks
Himanshu

RE: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Madhani, Himanshu]

Hi Nic/Bart, 

Can we get some review comments for this series. 

Thanks, 
Himanshu

> -Original Message-
> From: Himanshu Madhani [mailto:himanshu.madh...@cavium.com]
> Sent: Friday, February 24, 2017 1:37 PM
> To: target-de...@vger.kernel.org; bart.vanass...@sandisk.com;
> n...@linux-iscsi.org
> Cc: Malavali, Giridhar <giridhar.malav...@cavium.com>; linux-
> s...@vger.kernel.org; Madhani, Himanshu
> <himanshu.madh...@cavium.com>
> Subject: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.
> 
> Hi Nic,
> 
> Please consider this series for inclusion in target-pending.
> 
> This series contains following changes.
> 
> o Fix for the deadlock because of inconsistent lock usage reported by you.
> o Added patch to submit non-critical MBX command via IOCB path.
> o Improved T10-DIF/PI handling with target stack.
> o Changed scsi host lookup method.
> o Some minor bug fixes.
> 
> Changes from v2 --> v3
> 
> o Updated patch to use waitq instead of while loop for waiting.
> o Removed duplication of Target stack definitations for T10-DIF/PI.
> o In addition, addressed review comments from Bart & Christoph.
> 
> Changes from v1 -> v2
> 
> o Rebased series based on scsi-target-for-v4.11 branch.
> 
> Please apply to target-pending.
> 
> Thanks,
> Himanshu
> 
> Anil Gurumurthy (1):
>   qla2xxx: Export DIF stats via debugfs
> 
> Himanshu Madhani (2):
>   qla2xxx: Add DebugFS node to display Port Database
>   qla2xxx: Update driver version to 9.00.00.00-k
> 
> Joe Carnuccio (1):
>   qla2xxx: Allow vref count to timeout on vport delete.
> 
> Quinn Tran (10):
>   qla2xxx: Fix delayed response to command for loop mode/direct connect.
>   qla2xxx: Allow relogin to proceed if remote login did not finish
>   qla2xxx: Use IOCB interface to submit non-critical MBX.
>   qla2xxx: Improve T10-DIF/PI handling in driver.
>   qla2xxx: Change scsi host lookup method.
>   qla2xxx: Fix memory leak for abts processing
>   qla2xxx: Fix request queue corruption.
>   qla2xxx: Fix inadequate lock protection for ABTS.
>   qla2xxx: Add async new target notification
>   qla2xxx: Fix sess_lock & hardware_lock lock order problem.
> 
>  drivers/scsi/qla2xxx/Kconfig   |   1 +
>  drivers/scsi/qla2xxx/qla_attr.c|   4 +-
>  drivers/scsi/qla2xxx/qla_dbg.h |   1 +
>  drivers/scsi/qla2xxx/qla_def.h |  46 ++-
>  drivers/scsi/qla2xxx/qla_dfs.c | 115 +-
>  drivers/scsi/qla2xxx/qla_gbl.h |  12 +-
>  drivers/scsi/qla2xxx/qla_init.c|  85 ++---
>  drivers/scsi/qla2xxx/qla_isr.c |  41 ++-
>  drivers/scsi/qla2xxx/qla_mbx.c | 304 ++--
>  drivers/scsi/qla2xxx/qla_mid.c |  14 +-
>  drivers/scsi/qla2xxx/qla_os.c  |  24 +-
>  drivers/scsi/qla2xxx/qla_target.c  | 729 +++
> --
>  drivers/scsi/qla2xxx/qla_target.h  |  36 +-
>  drivers/scsi/qla2xxx/qla_version.h |   6 +-
>  drivers/scsi/qla2xxx/tcm_qla2xxx.c |  49 ++-
>  15 files changed, 1049 insertions(+), 418 deletions(-)
> 
> --
> 1.8.3.1

Re: [PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Bart Van Assche]

On Tue, 2017-02-28 at 22:00 +, Madhani, Himanshu wrote:
> Can we get some review comments for this series. 

Hello Himanshu,

The merge window opened one week ago and is still open. Anyone who contributes
to the Linux kernel should know that patches should not be posted during the
merge window because it's a busy time for most kernel contributors. 
Additionally,
no feedback should be expected during the merge window for patches that are not
bug fixes for changes that went in during the merge window. Anyway, I'll have a
look at these patches as soon as I have the time.

Bart.

[PATCH v3 00/14] qla2xxx: Bug Fixes and updates for target.

[Himanshu Madhani]

Hi Nic,

Please consider this series for inclusion in target-pending.

This series contains following changes.

o Fix for the deadlock because of inconsistent lock usage reported by you.
o Added patch to submit non-critical MBX command via IOCB path.
o Improved T10-DIF/PI handling with target stack.
o Changed scsi host lookup method.
o Some minor bug fixes.

Changes from v2 --> v3

o Updated patch to use waitq instead of while loop for waiting.
o Removed duplication of Target stack definitations for T10-DIF/PI.
o In addition, addressed review comments from Bart & Christoph.

Changes from v1 -> v2

o Rebased series based on scsi-target-for-v4.11 branch.

Please apply to target-pending.

Thanks,
Himanshu 

Anil Gurumurthy (1):
  qla2xxx: Export DIF stats via debugfs

Himanshu Madhani (2):
  qla2xxx: Add DebugFS node to display Port Database
  qla2xxx: Update driver version to 9.00.00.00-k

Joe Carnuccio (1):
  qla2xxx: Allow vref count to timeout on vport delete.

Quinn Tran (10):
  qla2xxx: Fix delayed response to command for loop mode/direct connect.
  qla2xxx: Allow relogin to proceed if remote login did not finish
  qla2xxx: Use IOCB interface to submit non-critical MBX.
  qla2xxx: Improve T10-DIF/PI handling in driver.
  qla2xxx: Change scsi host lookup method.
  qla2xxx: Fix memory leak for abts processing
  qla2xxx: Fix request queue corruption.
  qla2xxx: Fix inadequate lock protection for ABTS.
  qla2xxx: Add async new target notification
  qla2xxx: Fix sess_lock & hardware_lock lock order problem.

 drivers/scsi/qla2xxx/Kconfig   |   1 +
 drivers/scsi/qla2xxx/qla_attr.c|   4 +-
 drivers/scsi/qla2xxx/qla_dbg.h |   1 +
 drivers/scsi/qla2xxx/qla_def.h |  46 ++-
 drivers/scsi/qla2xxx/qla_dfs.c | 115 +-
 drivers/scsi/qla2xxx/qla_gbl.h |  12 +-
 drivers/scsi/qla2xxx/qla_init.c|  85 ++---
 drivers/scsi/qla2xxx/qla_isr.c |  41 ++-
 drivers/scsi/qla2xxx/qla_mbx.c | 304 ++--
 drivers/scsi/qla2xxx/qla_mid.c |  14 +-
 drivers/scsi/qla2xxx/qla_os.c  |  24 +-
 drivers/scsi/qla2xxx/qla_target.c  | 729 +++--
 drivers/scsi/qla2xxx/qla_target.h  |  36 +-
 drivers/scsi/qla2xxx/qla_version.h |   6 +-
 drivers/scsi/qla2xxx/tcm_qla2xxx.c |  49 ++-
 15 files changed, 1049 insertions(+), 418 deletions(-)

-- 
1.8.3.1