From: Jeff Garzik <jgarzik@pobox.com>
To: Mike Christie <mikenc@us.ibm.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Jens Axboe <axboe@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: dm core patches
Date: Wed, 18 Feb 2004 22:40:20 -0500 [thread overview]
Message-ID: <40343024.8000204@pobox.com> (raw)
In-Reply-To: <403402C1.50102@us.ibm.com>
Mike Christie wrote:
> diff -aurp linux-2.6.3-orig/include/linux/errno.h linux-2.6.3-ec/include/linux/errno.h
> --- linux-2.6.3-orig/include/linux/errno.h 2004-02-17 19:59:12.000000000 -0800
> +++ linux-2.6.3-ec/include/linux/errno.h 2004-02-18 12:45:42.000000000 -0800
> @@ -23,6 +23,14 @@
> #define EJUKEBOX 528 /* Request initiated, but will not complete before timeout */
> #define EIOCBQUEUED 529 /* iocb queued, will get completion event */
>
> +/* Block device error codes */
> +#define EFATALDEV 540 /* Fatal device error */
> +#define EFATALTRNSPT 541 /* Fatal transport error */
> +#define EFATALDRV 542 /* Fatal driver error */
> +#define ERETRYDEV 543 /* Device error occured, I/O may be retried */
> +#define ERETRYTRNSPT 544 /* Transport error occured, I/O may be retried */
> +#define ERETRYDRV 545 /* Driver error occured, I/O may be retried */
I'm not sure errno is the best place... I would rather define them in
blkdev.h and prefix them such that it's obvious they are specific to
block devices.
Also, WRT the I/O error printk, you probably want to print out a string
representing the error value returned... that info is available now,
might as well tell the user about it.
Jeff
next prev parent reply other threads:[~2004-02-19 3:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 16:44 dm core patches James Bottomley
2004-02-16 8:22 ` Lars Marowsky-Bree
2004-02-16 16:57 ` Jens Axboe
2004-02-16 17:04 ` James Bottomley
2004-02-19 0:26 ` Mike Christie
2004-02-19 3:40 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-10 16:35 Joe Thornber
2004-02-11 10:16 ` Lars Marowsky-Bree
2004-02-11 10:35 ` Joe Thornber
2004-02-12 18:51 ` Lars Marowsky-Bree
2004-02-12 20:13 ` Joe Thornber
2004-02-13 15:12 ` Lars Marowsky-Bree
2004-02-13 15:39 ` Joe Thornber
2004-02-13 16:08 ` Arjan van de Ven
2004-02-16 8:19 ` Lars Marowsky-Bree
2004-02-16 9:35 ` Arjan van de Ven
2004-02-13 23:46 ` Mike Anderson
2004-02-16 12:17 ` Heinz Mauelshagen
2004-02-13 16:03 ` Jens Axboe
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=40343024.8000204@pobox.com \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@steeleye.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikenc@us.ibm.com \
/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.