From: Raghava Aditya Renukunta <RaghavaAditya.Renukunta@microsemi.com>
To: Prasad Munirathnam <Prasad.Munirathnam@microsemi.com>Prasad
Munirathnam <Prasad.Munirathnam@microsemi.com>,
Dave Carroll <david.carroll@microsemi.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"james.bottomley@hansenpartnership.com"
<james.bottomley@hansenpartnership.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: RE: [PATCH] scsi: aacraid: fix io drop during the reset
Date: Wed, 13 Dec 2017 21:23:54 +0000 [thread overview]
Message-ID: <c2a7ecdf480c4946aa5571469685802c@microsemi.com> (raw)
In-Reply-To: <1513107610-24451-1-git-send-email-prasad.munirathnam@microsemi.com>
> -----Original Message-----
> From: Prasad B Munirathnam [mailto:prasad.munirathnam@microsemi.com]
> Sent: Tuesday, December 12, 2017 11:40 AM
> To: Prasad Munirathnam <Prasad.Munirathnam@microsemi.com>; Dave
> Carroll <david.carroll@microsemi.com>; Raghava Aditya Renukunta
> <RaghavaAditya.Renukunta@microsemi.com>;
> martin.petersen@oracle.com; james.bottomley@hansenpartnership.com
> Cc: linux-scsi@vger.kernel.org
> Subject: [PATCH] scsi: aacraid: fix io drop during the reset
>
> "FIB_CONTEXT_FLAG_TIMEDOUT" flag is set in aac_eh_abort to
> indicate command timeout, using the same flag in reset handler
> causes the command to timeout and the IO's were droped.
>
> defined a new flag "FIB_CONTEXT_FLAG_EH_RESET" to make sure IO
> is properly handled in eh_reset handler.
>
> Signed-off-by: Prasad B Munirathnam
> <prasad.munirathnam@microsemi.com>
> ---
Reviewed-by :Raghava Aditya Renukunta <RaghavaAditya.Renukunta@microsemi.com>
next prev parent reply other threads:[~2017-12-13 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 19:40 [PATCH] scsi: aacraid: fix io drop during the reset Prasad B Munirathnam
2017-12-13 21:23 ` Raghava Aditya Renukunta [this message]
2017-12-15 3:34 ` 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=c2a7ecdf480c4946aa5571469685802c@microsemi.com \
--to=raghavaaditya.renukunta@microsemi.com \
--cc=Prasad.Munirathnam@microsemi.com \
--cc=linux-scsi@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 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).