public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	"Stephen C. Tweedie" <sct@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: DVD blockdevice buffers
Date: Thu, 24 May 2001 00:24:52 +0200	[thread overview]
Message-ID: <20010524002452.B764@athlon.random> (raw)
In-Reply-To: <20010524000933.A764@athlon.random> <Pine.GSO.4.21.0105231812210.20269-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0105231812210.20269-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Wed, May 23, 2001 at 06:13:13PM -0400

On Wed, May 23, 2001 at 06:13:13PM -0400, Alexander Viro wrote:
> Uh-oh... After you solved what?

The superblock is pinned by the kernel in buffercache while you fsck a
ro mounted ext2, so I must somehow uptodate this superblock in the
buffercache before collecting away the pagecache containing more recent
info from fsck. It's all done lazily, I just thought not to break the
assumption that an idling buffercache will never become not uptodate
under you anytime because it seems not too painful to implement compared
to changing the fs, it puts the check in a slow path and it doesn't
break the API with the buffercache (so I don't need to change all the fs
to check if the superblock is still uptodate before marking it dirty).

Andrea

  reply	other threads:[~2001-05-23 22:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-18 19:02 DVD blockdevice buffers Eduard Hasenleithner
2001-05-18 19:25 ` Jens Axboe
2001-05-18 19:59   ` Eduard Hasenleithner
2001-05-20  2:36   ` Linus Torvalds
2001-05-23 17:34     ` Stephen C. Tweedie
2001-05-23 18:12       ` Linus Torvalds
2001-05-23 19:57         ` Stephen C. Tweedie
2001-05-23 20:01           ` Linus Torvalds
2001-05-23 20:40             ` Jeff Garzik
2001-05-23 22:32               ` Andrea Arcangeli
2001-05-25 20:12                 ` blkdev-pagecache-2 [was Re: DVD blockdevice buffers] Andrea Arcangeli
2001-05-25 20:15                   ` Andrea Arcangeli
2001-05-23 22:09             ` DVD blockdevice buffers Andrea Arcangeli
2001-05-23 22:13               ` Alexander Viro
2001-05-23 22:24                 ` Andrea Arcangeli [this message]
2001-05-24 11:36             ` Stephen C. Tweedie
2001-05-25 15:09               ` Eric W. Biederman
2001-05-25 15:45                 ` Stephen C. Tweedie
2001-05-25 17:16                 ` Linus Torvalds
2001-05-25 17:40                   ` Alexander Viro
2001-05-25 18:05                     ` Linus Torvalds
2001-05-25 18:24                       ` Alexander Viro
2001-05-25 19:02                         ` Stephen C. Tweedie
2001-05-27  6:38                     ` Pavel Machek
2001-05-25 21:07                   ` Eric W. Biederman
2001-05-25 21:18                     ` Linus Torvalds
2001-05-25 22:31                       ` Eric W. Biederman
  -- strict thread matches above, loose matches on Subject: below --
2001-05-19 18:16 Adam Schrotenboer
2001-05-19 22:56 ` Jens Axboe
2001-05-20  1:55   ` Adam Schrotenboer
2001-05-21 15:44   ` Adam Schrotenboer
2001-05-21 15:47     ` Jens Axboe

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=20010524002452.B764@athlon.random \
    --to=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