From: Douglas Gilbert <dougg@torque.net>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] normalize fixed and descriptor sense data
Date: Sat, 28 Aug 2004 14:07:45 +1000 [thread overview]
Message-ID: <41300511.2060303@torque.net> (raw)
In-Reply-To: <3DD91260-F839-11D8-A52F-00039398BB5E@ieee.org>
Pat LaVarre wrote:
> Doug G:
>
> > so deferred errors can
> > be ignored in many contexts
>
> Any hope of Linux always reporting that deferred errors have occurred,
> at least via dmesg if not in a critical dialog?
I certainly hope so. One small change I made in my patch
yesterday was to pass deferred errors back to the block
SG_IO code.
This could be a largish job. First put a more robust
mechanism in place, then sweep the scsi mid level and
perhaps upper level drivers and convert them to the
new interface. The important thing to do is to think
about the error checking code distributed around the
place. It is reasonably easy to fix the wrong headed
stuff but wider issues are often involved (e.g. should
this be ignored and/or processed at a different level).
> A deferred error, in the context of sense data ((bytes[0] & x7F) != x70)
> is usually a purportedly rare and therefore interesting catastrophe of
> some kind, yes? A failure to write seen while flushing cache. A
> failure to eject after obediently faking "immediate"ly good status. Etc.
>
> > http://marc.theaimsgroup.com/?l=linux-scsi&m=109359716220586
Perhaps deferred errors should be picked up at the lowest
level of the midlevel, logged and ignored at higher levels
unless they are going back to a pass through interface.
> Sorry I failed to click thru to the context for this thread.
That is fine, the only other folks that I seemed to wake up
were the style police :-)
Doug Gilbert
next prev parent reply other threads:[~2004-08-28 4:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 14:56 [PATCH] normalize fixed and descriptor sense data Pat LaVarre
2004-08-28 4:07 ` Douglas Gilbert [this message]
2004-08-28 6:31 ` Kai Makisara
[not found] ` <3CC78E D C-FAAA-11D8-85F1-00039398BB5E@ieee.org>
2004-08-30 17:30 ` Pat LaVarre
2004-08-30 19:51 ` Kai Makisara
2004-08-30 20:03 ` Pat LaVarre
-- strict thread matches above, loose matches on Subject: below --
2004-08-27 8:56 Douglas Gilbert
2004-08-27 15:18 ` Christoph Hellwig
2004-08-27 15:45 ` Luben Tuikov
2004-08-27 15:52 ` Christoph Hellwig
2004-08-27 15:46 ` Randy.Dunlap
2004-08-28 5:05 ` Douglas Gilbert
2004-08-28 20:23 ` Christoph Hellwig
2004-08-29 0:36 ` Douglas Gilbert
2004-08-29 8:59 ` 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=41300511.2060303@torque.net \
--to=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=p.lavarre@ieee.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