From: Andrew Morton <akpm@zip.com.au>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Alexander Viro <viro@math.psu.edu>,
Linus Torvalds <torvalds@transmeta.com>,
Andrea Arcangeli <andrea@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Patch: aliasing bug in blockdev-in-pagecache?
Date: Sat, 13 Apr 2002 16:16:02 -0700 [thread overview]
Message-ID: <3CB8BC32.51231352@zip.com.au> (raw)
In-Reply-To: <20020413235948.E4937@redhat.com>
"Stephen C. Tweedie" wrote:
>
> ...
> --- fs/buffer.c.~1~ Fri Apr 12 17:59:09 2002
> +++ fs/buffer.c Sat Apr 13 21:09:36 2002
> @@ -1902,9 +1902,14 @@
> }
>
> /* Stage 3: start the IO */
> - for (i = 0; i < nr; i++)
> - submit_bh(READ, arr[i]);
> -
> + for (i = 0; i < nr; i++) {
> + struct buffer_head * bh = arr[i];
> + if (buffer_uptodate(bh))
> + end_buffer_io_async(bh, 1);
> + else
> + submit_bh(READ, bh);
> + }
> +
> return 0;
> }
>
Agree. I have debug checks for this in the 2.5 code and
they do not come out in normal use, so no probs there.
I'm starting to tighten all of this up in the patches
which I'm working on. Move the debug checks out of
ll_rw_block and into submit_bh. submit_bh will complain about
- writing non-uptodate buffer
- reading uptodate buffer
- reading dirty buffer
- reading or writing unmapped buffer
- anything else I can think of.
This means that a number of callers need to be changed
to set the bits correctly, which is pointless work.
But really, I think we need that formality - we keep on
making obscure mistakes in this area and the costs are
high.
-
next prev parent reply other threads:[~2002-04-13 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-13 22:59 [RFC] Patch: aliasing bug in blockdev-in-pagecache? Stephen C. Tweedie
2002-04-13 23:16 ` Andrew Morton [this message]
2002-04-14 12:59 ` Alexander Viro
2002-04-14 13:08 ` Stephen C. Tweedie
2002-04-16 18:01 ` Andrea Arcangeli
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=3CB8BC32.51231352@zip.com.au \
--to=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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