mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Cinege <dcinege@psychosis.com>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] invalidate buffers on blkdev_put
Date: Mon, 1 Oct 2001 16:02:51 -0400	[thread overview]
Message-ID: <E15o9FF-0005Ve-00@schizo.psychosis.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0109242333240.21827-100000@weyl.math.psu.edu> <Pine.LNX.4.33.0109242118540.29038-100000@penguin.transmeta.com> <20010927140312.A35@toy.ucw.cz>
In-Reply-To: <20010927140312.A35@toy.ucw.cz>

On Thursday 27 September 2001 10:03, Pavel Machek wrote:
> Hi!
>
> > > It's solvable, but not obvious.  It _does_ solve coherency problems
> > > between device page cache and buffer cache (thus killing
> > > update_buffers() and its ilk), but the last issue (new access path to
> > > page-private buffer_heads) may be rather nasty.
> >
> > It's certainly solvable, but it is also certainly very fraught with tons
> > of small details. I'll be very happy if people end up looking through the
> > patches _very_ critically (and don't even bother testing them if you
> > don't have a machine where you can lose a filesystem or two).
>
> Time to rename 2.4.10 to 2.5.0? ;-)

<Waving hand> It broke my feature patch. Good enough for me.  ; >

-- 
The time is now 22:19 (Totalitarian)  -  http://www.ccops.org/clock.html

  reply	other threads:[~2001-10-01 20:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25  3:18 Chris Mason
2001-09-25  3:52 ` Alexander Viro
2001-09-25  4:21   ` Linus Torvalds
2001-09-27 14:03     ` Pavel Machek
2001-10-01 20:02       ` Dave Cinege [this message]
2001-09-25 22:59   ` Anton Altaparmakov
2001-09-26  3:39     ` Linus Torvalds
2001-09-26 22:42     ` Anton Altaparmakov
2001-09-27  0:03       ` Andreas Dilger

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=E15o9FF-0005Ve-00@schizo.psychosis.com \
    --to=dcinege@psychosis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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

all inboxes | Powered by JetHome®