From: Hannes Reinecke <hare@suse.de>
To: Sumit Saxena <sumit.saxena@broadcom.com>,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, hch@infradead.org, thenzl@redhat.com
Cc: kashyap.desai@broadcom.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/4] megaraid_sas: call ISR function to clean up pending replies in OCR path
Date: Fri, 15 Apr 2016 16:12:24 +0200 [thread overview]
Message-ID: <5710F6C8.4020108@suse.de> (raw)
In-Reply-To: <1460705013-6482-3-git-send-email-sumit.saxena@broadcom.com>
On 04/15/2016 09:23 AM, Sumit Saxena wrote:
> In OCR path, before calling chip reset calls function megasas_wait_for_outstanding_fusion to check reason
> of OCR. In case of firmware FAULT initiated OCR and DCMD timeout initiated timeout, driver will clear any
> outstanding reply(yet to be processed by driver) in reply queues before going for chip reset.
> This code is added to handle a scenario when IO timeout initiated adapter reset and management application
> initiated adapter reset(by sending command to FAULT firmware) happens simultaneously since adapter reset
> function is safe-guarded by reset_mutex so only thread will be doing controller reset. Consider IO timeout
> thread gets mutex and proceeds with adapter reset process after disabling interrupts and by the time
> managementapplication has fired command to firmware to do adapter reset and the same command is completed by
> firmware but since interrupts are disabled, driver will not get completion and the same command will be in
> outstanding/pendingcommands list of driver and refires same command from IO timeout thread after chip reset
> which will again FAULT firmware and evntually causes kill adapter.
>
> Signed-off-by: Sumit Saxena <sumit.saxena@broadcom.com>
> ---
> drivers/scsi/megaraid/megaraid_sas_fusion.c | 2 ++
> 1 file changed, 2 insertions(+)
>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-04-15 14:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 7:23 [PATCH 0/4] megaraid_sas: Updates for scsi-next Sumit Saxena
2016-04-15 7:23 ` [PATCH 1/4] megaraid_sas: reduce memory footprints in kdump mode Sumit Saxena
2016-04-15 14:11 ` Hannes Reinecke
2016-04-15 7:23 ` [PATCH 2/4] megaraid_sas: call ISR function to clean up pending replies in OCR path Sumit Saxena
2016-04-15 14:12 ` Hannes Reinecke [this message]
2016-04-15 7:23 ` [PATCH 3/4] megaraid_sas: task management code optimizations Sumit Saxena
2016-04-15 14:13 ` Hannes Reinecke
2016-04-15 7:23 ` [PATCH 4/4] megaraid_sas: driver version upgrade Sumit Saxena
2016-04-15 14:13 ` Hannes Reinecke
2016-04-15 20:34 ` [PATCH 0/4] megaraid_sas: Updates for scsi-next 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=5710F6C8.4020108@suse.de \
--to=hare@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hch@infradead.org \
--cc=kashyap.desai@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sumit.saxena@broadcom.com \
--cc=thenzl@redhat.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).