From: Linus Torvalds <torvalds@transmeta.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: <Stefan.Bader@de.ibm.com>, <linux-kernel@vger.kernel.org>
Subject: Re: correction: fs/buffer.c underlocking async pages
Date: Thu, 21 Jun 2001 11:49:20 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0106211148140.1506-100000@penguin.transmeta.com> (raw)
In-Reply-To: <20010621191522.B28327@athlon.random>
On Thu, 21 Jun 2001, Andrea Arcangeli wrote:
> On Thu, Jun 21, 2001 at 09:56:04AM -0700, Linus Torvalds wrote:
> What's the problem with the existing code, and why do people want to add a
> > (unnecessary) new bit?
>
> there's no problem with the existing code, what I understood is that
> they cannot overwrite the ->b_end_io callback in the lowlevel blkdev
> layer or the page will be unlocked too early.
Oh, fair enough.
I don't have any objections to the patch in that case, although it does
end up being a 2.5.x issue as far as I'm concerned (and don't worry, 2.5.x
looks like it will open in a week or two, so we're not talking about long
timeframes).
Obviously 2.5.x code may be back-ported to 2.4.x later. That will be up to
Alan.
Linus
next prev parent reply other threads:[~2001-06-21 18:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 14:39 correction: fs/buffer.c underlocking async pages Stefan.Bader
2001-06-21 15:08 ` Andrea Arcangeli
2001-06-21 15:16 ` Chris Mason
2001-06-21 15:24 ` Andrea Arcangeli
2001-06-21 16:54 ` Linus Torvalds
2001-06-21 17:12 ` Andrea Arcangeli
2001-06-21 15:38 ` Andrea Arcangeli
2001-06-21 16:56 ` Linus Torvalds
2001-06-21 17:15 ` Andrea Arcangeli
2001-06-21 17:58 ` Andrea Arcangeli
2001-06-21 18:20 ` Chris Mason
2001-06-21 18:49 ` Linus Torvalds [this message]
2001-06-22 7:43 Stefan.Bader
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=Pine.LNX.4.33.0106211148140.1506-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=Stefan.Bader@de.ibm.com \
--cc=andrea@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).