* [RFC]: scsi_error: interruptible scsi_block_when_processing_errors()
@ 2013-10-23 16:02 Douglas Gilbert
0 siblings, 0 replies; only message in thread
From: Douglas Gilbert @ 2013-10-23 16:02 UTC (permalink / raw)
To: SCSI development list
The existing scsi_block_when_processing_errors() function
in scsi_error.c does a non-interruptible wait on the
host_wait work queue. That call is made from many places
in the scsi subsystem ULDs (e.g. the sg driver).
In many cases (e.g. sg_open()) there is a direct path
back to the user space. So why hang open(sg_device) calls
(that don't use O_NONBLOCK) in an non-interruptible call
for what might be a long time.
Apart from signal indications, such a non-interruptible
version of scsi_block_when_processing_errors() could return
useful (possibly negated) errno_s, for example indicating
the device in question had been detached or timed out
(possibly because the HBA was being reset).
Thoughts?
Doug Gilbert
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-10-23 16:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-23 16:02 [RFC]: scsi_error: interruptible scsi_block_when_processing_errors() Douglas Gilbert
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.