From: Mike Christie <michaelc@cs.wisc.edu>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2][RFC] add detailed error values to block layer
Date: Thu, 18 Mar 2004 06:02:40 -0800 [thread overview]
Message-ID: <4059AC00.6020409@cs.wisc.edu> (raw)
I saw that the Adaptec RAID developers are in need of detailed IO
error values too, so I wanted to post what I have so we can try to
work together. I have converted the block layer, but have not finished
the end request callers.
01-ec-core.patch just defines the error values, and modifies the request
completion functions. Right now they just convert the uptodate status to
an error value. Per Jeff's advice I did not define my own erronos.
wrt his other comment, I was not sure if wanted me to print the error
value in string form in __end_that_request, or just print the numerical
value.
02-ec-bioendio.patch converts the bio_endio and bi_end_io
callers to pass one of the error values defined above instead of
the -Exxx.
Both patches were built against 2.6.5-rc1.
The block layer error values are not too exciting. There were very few
drivers that did not just return EIO. The end request users
will be much more fun :)
Thanks,
Mike Chrisite
reply other threads:[~2004-03-18 14:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4059AC00.6020409@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=linux-kernel@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