Re: [PATCH] qla2xxx: Add fix for hardware lock/unlock issue.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks,
-Himanshu





On 4/23/15, 1:21 PM, "Greg KH" <greg@xxxxxxxxx> wrote:

>On Thu, Apr 23, 2015 at 03:12:00PM -0400, Himanshu Madhani wrote:
>> From: Saurav Kashyap <saurav.kashyap@xxxxxxxxxx>
>>
>> This patch fixes a kernel panic for qla2xxx Target core
>> Module driver introduced by a fix in the qla2xxx initiator code.
>>
>> Commit ef86cb2059a14b4024c7320999ee58e938873032 introduced the
>> regression for qla2xxx Target driver. Stack trace will have following
>>signature
>>
>> --- <NMI exception stack> ---
>> [ffff88081faa3cc8] _raw_spin_lock_irqsave at ffffffff815b1f03
>> [ffff88081faa3cd0] qlt_fc_port_deleted at ffffffffa096ccd0 [qla2xxx]
>> [ffff88081faa3d20] qla2x00_schedule_rport_del at
>>ffffffffa0913831[qla2xxx]
>> [ffff88081faa3d50] qla2x00_mark_device_lost at ffffffffa09159c5[qla2xxx]
>> [ffff88081faa3db0] qla2x00_async_event at ffffffffa0938d59 [qla2xxx]
>> [ffff88081faa3e30] qla24xx_msix_default at ffffffffa093a326 [qla2xxx]
>> [ffff88081faa3e90] handle_irq_event_percpu at ffffffff810a7b8d
>> [ffff88081faa3ee0] handle_irq_event at ffffffff810a7d32
>> [ffff88081faa3f10] handle_edge_irq at ffffffff810ab6b9
>> [ffff88081faa3f30] handle_irq at ffffffff8100619c
>> [ffff88081faa3f70] do_IRQ at ffffffff815b4b1c
>> --- <IRQ stack> ---
>>
>> Cc: stable@xxxxxxxxxxxxxxx
>> Signed-off-by: Saurav Kashyap <saurav.kashyap@xxxxxxxxxx>
>> Signed-off-by: Himanshu Madhani <himanshu.madhani@xxxxxxxxxx>
>> ---
>>  drivers/scsi/qla2xxx/qla_init.c   |    4 ++++
>>  drivers/scsi/qla2xxx/qla_target.c |    6 ------
>>  2 files changed, 4 insertions(+), 6 deletions(-)
>
>
><formletter>
>
>This is not the correct way to submit patches for inclusion in the
>stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
>for how to do this properly.
>
></formletter>

 I will resubmit patch with correction.

>


________________________________

This message and any attached documents contain information from the sending company or its parent company(s), subsidiaries, divisions or branch offices that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message.
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]