Messages in this thread | | | Date | Fri, 18 Feb 2005 21:17:13 +0100 | From | Kay Sievers <> | Subject | Re: [PATCH] add I/O error uevent for block devices |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |