From: Kay Sievers <kay.sievers@vrfy.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com, david@fubar.dk
Subject: Re: [PATCH] add I/O error uevent for block devices
Date: Fri, 18 Feb 2005 21:17:13 +0100 [thread overview]
Message-ID: <20050218201713.GA9084@vrfy.org> (raw)
In-Reply-To: <20050218110232.6512f0fb.akpm@osdl.org>
On Fri, Feb 18, 2005 at 11:02:32AM -0800, Andrew Morton wrote:
> Kay Sievers <kay.sievers@vrfy.org> wrote:
> >
> > > - there are numerous other places where an I/O error can be detected:
> > > grep the tree for b_end_io and bio_end_io.
> >
> > You mean the mmap and direct-io stuff?
>
> direct-io, certainly. Also reiserfs, xfs, ntfs, ext3, jfs and possibly md
> have their own I/O completion handlers.
Hmm, ok. Any idea how to propagate errors like this in a saner way? Some of
these places don't even log errors and spreading uevents all over the place
doesn't sounds like the best idea.
Thanks,
Kay
next prev parent reply other threads:[~2005-02-18 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 8:33 [PATCH] add I/O error uevent for block devices Kay Sievers
2005-02-18 9:46 ` Andrew Morton
2005-02-18 12:45 ` Kay Sievers
2005-02-18 19:02 ` Andrew Morton
2005-02-18 20:17 ` Kay Sievers [this message]
2005-02-18 20:41 ` Andrew Morton
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=20050218201713.GA9084@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=akpm@osdl.org \
--cc=david@fubar.dk \
--cc=greg@kroah.com \
--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