From: Andrew Morton <akpm@digeo.com>
To: Oliver Xymoron <oxymoron@waste.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5] Report write errors to applications
Date: Thu, 30 Jan 2003 14:13:54 -0800 [thread overview]
Message-ID: <3E39A3A2.7807FF00@digeo.com> (raw)
In-Reply-To: 20030130220011.GC4357@waste.org
Oliver Xymoron wrote:
>
> The comment suggests that we need to distinguish read errors from
> write errors and I tend to agree.
OK, well you could call set_buffer_write_io_error/set_buffer_read_io_error()
in the end_io handlers, and pick that up later on.
To avoid adding a couple of new clear_bits in submit_bh,
you could do:
if (test_set_buffer_req(bh)) {
clear_buffer_write_io_error(bh);
clear_buffer_read_io_error(bh);
}
next prev parent reply other threads:[~2003-01-30 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 6:09 [PATCH 2.5] Report write errors to applications Oliver Xymoron
2003-01-29 7:29 ` Andrew Morton
2003-01-29 16:24 ` Oliver Xymoron
2003-01-29 21:42 ` Andrew Morton
2003-01-30 21:12 ` Oliver Xymoron
2003-01-30 21:39 ` Andrew Morton
2003-01-30 22:00 ` Oliver Xymoron
2003-01-30 22:13 ` Andrew Morton [this message]
2003-01-31 18:42 ` Oliver Xymoron
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=3E39A3A2.7807FF00@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.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