From: Chris Mason <mason@suse.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Alan Cox <alan@redhat.com>,
Stefan Traby <stefan@hello-penguin.com>,
linux-kernel@vger.kernel.org
Subject: Re: ramfs problem... (unlink of sparse file in "D" state)
Date: Mon, 08 Jan 2001 11:11:55 -0500 [thread overview]
Message-ID: <97890000.978970315@tiny> (raw)
In-Reply-To: <Pine.GSO.4.21.0101081042490.4061-100000@weyl.math.psu.edu>
On Monday, January 08, 2001 10:47:41 AM -0500 Alexander Viro
<viro@math.psu.edu> wrote:
> + do {
> + if (buffer_mapped(bh)) {
> + bh->b_end_io = end_buffer_io_async;
> + atomic_inc(&bh->b_count);
> + set_bit(BH_Uptodate, &bh->b_state);
> + set_bit(BH_Dirty, &bh->b_state);
^^^^^^^
Sorry, missed this the first time I read it. We need to clear the dirty bit
before sending to submit_bh, otherwise it stays dirty until
try_to_free_buffers writes it again.
> + submit_bh(WRITE, bh);
> + }
> + bh = bh->b_this_page;
> + } while (bh != head);
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-08 16:12 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 4:46 ramfs problem... (unlink of sparse file in "D" state) Stefan Traby
2001-01-06 4:52 ` Alexander Viro
2001-01-06 5:08 ` Stefan Traby
2001-01-06 5:18 ` Alexander Viro
2001-01-06 5:24 ` modprobe ipv6 gives -1 usage count was [ramfs problem...] Stefan Traby
2001-01-06 9:55 ` Russell King
2001-01-06 11:05 ` Matti Aarnio
2001-01-06 15:35 ` Alan Cox
2001-01-06 15:35 ` ramfs problem... (unlink of sparse file in "D" state) Alan Cox
2001-01-06 15:53 ` Chris Wedgwood
2001-01-06 15:58 ` Alan Cox
2001-01-06 16:07 ` Chris Wedgwood
2001-01-07 7:05 ` Eric W. Biederman
2001-01-07 8:08 ` Chris Wedgwood
2001-01-07 14:01 ` Alan Cox
2001-01-07 13:57 ` Alan Cox
2001-01-07 14:07 ` Chris Wedgwood
2001-01-07 14:20 ` Alan Cox
2001-01-07 14:56 ` Eric W. Biederman
2001-01-08 7:56 ` Alexander Viro
2001-01-08 8:12 ` Chris Wedgwood
2001-01-08 8:41 ` [PATCH(es)] " Alexander Viro
2001-01-08 11:50 ` Alan Cox
2001-01-08 7:50 ` Alexander Viro
2001-01-08 11:46 ` Alan Cox
2001-01-08 11:50 ` Alexander Viro
2001-01-08 12:09 ` Alan Cox
2001-01-08 12:16 ` Alexander Viro
2001-01-08 12:26 ` Alan Cox
2001-01-08 13:17 ` Stefan Traby
2001-01-08 13:35 ` Alexander Viro
2001-01-08 14:00 ` Stefan Traby
2001-01-08 14:19 ` Alexander Viro
2001-01-08 14:40 ` Alan Cox
2001-01-08 14:52 ` Alexander Viro
2001-01-08 15:09 ` Alan Cox
2001-01-08 15:32 ` Alexander Viro
2001-01-08 15:55 ` Stefan Traby
2001-01-08 16:01 ` Alan Cox
2001-01-08 16:22 ` Stefan Traby
2001-01-08 17:10 ` Alan Cox
2001-01-08 18:05 ` Alexander Viro
2001-01-08 18:18 ` Stefan Traby
2001-01-08 18:22 ` Alexander Viro
2001-01-08 18:24 ` Stefan Traby
2001-01-08 18:33 ` Alexander Viro
2001-01-08 18:51 ` Stefan Traby
2001-01-08 18:54 ` Marc Lehmann
2001-01-08 19:07 ` Alexander Viro
2001-01-08 14:02 ` Alexander Viro
2001-01-08 15:37 ` Chris Mason
2001-01-08 15:47 ` Alexander Viro
2001-01-08 16:11 ` Chris Mason [this message]
2001-01-08 17:35 ` Alexander Viro
2001-01-08 17:50 ` Alan Cox
2001-01-08 19:07 ` Andreas Dilger
2001-01-08 20:12 ` Alexander Viro
2001-01-08 20:38 ` Andreas Dilger
2001-01-08 13:37 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-01-08 21:34 Andries.Brouwer
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=97890000.978970315@tiny \
--to=mason@suse.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan@hello-penguin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.