From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"krisman@linux.vnet.ibm.com" <krisman@linux.vnet.ibm.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"brking@linux.vnet.ibm.com" <brking@linux.vnet.ibm.com>,
"gabriel@krisman.be" <gabriel@krisman.be>
Subject: Re: [PATCH v3 1/2] scsi: Handle Unit Attention when issuing SCSI command
Date: Wed, 26 Oct 2016 16:15:22 +0000 [thread overview]
Message-ID: <1477498520.2550.1.camel@sandisk.com> (raw)
In-Reply-To: <1477497160.2724.11.camel@linux.vnet.ibm.com>
On Wed, 2016-10-26 at 08:52 -0700, James Bottomley wrote:
> On Wed, 2016-10-26 at 08:42 -0700, Bart Van Assche wrote:
> > Can you elaborate on this? Since the sense buffer is available in
> > scsi_io_completion() and since that function already calls
> > scsi_command_normalize_sense() this function seems like a good
> > candidate to me to add retry logic for REQ_TYPE_BLOCK_PC requests.
>
> UAs are used to signal AENs to userspace control processes that use
> BLOCK_PC, like CD changers, burners and scanners. If we eat UAs
> inside scsi_io_completion(), we could potentially break any userspace
> control system that relies on AENs.
Ignoring the SCSI error handler, the call sequence for reporting UAs to
user space is as follows: scsi_softirq_done() ->
scsi_decide_disposition() -> scsi_check_sense() -> scsi_report_sense().
This means that scsi_report_sense() is called before
scsi_io_completion() is called. I think this means that what
scsi_io_completion() decides cannot affect UA reporting to user space?
Bart.
next prev parent reply other threads:[~2016-10-26 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 3:20 [PATCH v3 1/2] scsi: Handle Unit Attention when issuing SCSI command Gabriel Krisman Bertazi
2016-10-24 3:20 ` [PATCH v3 2/2] scsi: sr: Drop custom handling of unit attention Gabriel Krisman Bertazi
2016-10-25 13:00 ` [PATCH v3 1/2] scsi: Handle Unit Attention when issuing SCSI command Benjamin Block
2016-10-25 22:16 ` Bart Van Assche
2016-10-25 22:23 ` James Bottomley
2016-10-25 23:18 ` Bart Van Assche
2016-10-25 23:50 ` James Bottomley
2016-10-26 15:42 ` Bart Van Assche
2016-10-26 15:52 ` James Bottomley
2016-10-26 16:15 ` Bart Van Assche [this message]
2016-10-26 17:38 ` Brian King
2016-10-27 9:00 ` Hannes Reinecke
2016-10-28 7:32 ` Christoph Hellwig
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=1477498520.2550.1.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=brking@linux.vnet.ibm.com \
--cc=gabriel@krisman.be \
--cc=jejb@linux.vnet.ibm.com \
--cc=krisman@linux.vnet.ibm.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 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.