From: Linus Torvalds <torvalds@transmeta.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Viro <aviro@redhat.com>,
Andrew Morton <andrewm@uow.edu.au>,
"Stephen C. Tweedie" <sct@redhat.com>, Alan Cox <alan@redhat.com>,
Christoph Rohland <cr@sap.com>,
Rik van Riel <riel@conectiva.com.br>,
MOLNAR Ingo <mingo@chiara.elte.hu>
Subject: Re: test12-pre5
Date: Mon, 4 Dec 2000 20:00:03 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.10.10012041955000.860-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0012042232220.7166-100000@weyl.math.psu.edu>
On Mon, 4 Dec 2000, Alexander Viro wrote:
>
> On Mon, 4 Dec 2000, Linus Torvalds wrote:
> >
> > Ok, this contains one of the fixes for the dirty inode buffer list (the
> > other fix is pending, simply because I still want to understand why it
> > would be needed at all). Al?
>
> See previous posting. BTW, -pre5 doesn't do the right thing in clear_inode().
>
> Scenario: bh of indirect block is busy (whatever reason, flush_dirty_buffers(),
> anything that can bump ->b_count for a while). ext2_truncate() frees the
> thing and does bforget(). bh is left on the inode's list. Woops...
So? Why wouldn't clear_inode() get rid of it?
> The minimal fix would be to make clear_inode() empty the list. IMO it's
> worse than preventing the freed stuff from being on that list...
This _is_ what clear_inode() does in pre5 (and in pre4, for that matter):
void clear_inode(struct inode *inode)
{
if (!list_empty(&inode->i_dirty_buffers))
invalidate_inode_buffers(inode);
...
which I find perfectly readable. And should mean that no dirty buffers
should be associated with the inode any more. ext2 calls clear_inode()
from ext2_free_inode(), and as far as I can tell the only thing that can
happen after that is that the inode is still scheduled for write-out
(which explains how the bug you fixed would cause a dirty block to be
attached to the inode _after_ we did a clear_inode() on it).
Or are you thinking of something else?
Linus
-
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:[~2000-12-05 4:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-05 3:20 test12-pre5 Linus Torvalds
2000-12-05 3:42 ` test12-pre5 Alexander Viro
2000-12-05 4:00 ` Linus Torvalds [this message]
2000-12-05 4:25 ` test12-pre5 Alexander Viro
2000-12-05 17:09 ` test12-pre5 Stephen C. Tweedie
2000-12-05 17:28 ` test12-pre5 Alexander Viro
2000-12-05 17:48 ` test12-pre5 Linus Torvalds
2000-12-05 18:14 ` test12-pre5 Alexander Viro
2000-12-05 18:33 ` test12-pre5 Linus Torvalds
2000-12-05 18:59 ` test12-pre5 Alexander Viro
2000-12-05 19:48 ` test12-pre5 Linus Torvalds
2000-12-05 20:17 ` test12-pre5 Alexander Viro
2000-12-05 23:15 ` test12-pre5 Stephen C. Tweedie
2000-12-05 18:50 ` test12-pre5 Stephen C. Tweedie
2000-12-05 5:30 ` test12-pre5 Mohammad A. Haque
2000-12-05 7:51 ` test12-pre5 Andrew Morton
2000-12-05 15:48 ` test12-pre5 Daniel Phillips
2000-12-05 23:25 ` smbfs writepage & struct file Urban Widmark
2000-12-05 23:57 ` Linus Torvalds
2000-12-10 13:43 ` Urban Widmark
2000-12-06 10:05 ` Trond Myklebust
2000-12-06 13:18 ` test12-pre5 Panu Matilainen
[not found] <00120522275601.09076@gimli>
2000-12-05 21:58 ` test12-pre5 Linus Torvalds
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.10.10012041955000.860-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=alan@redhat.com \
--cc=andrewm@uow.edu.au \
--cc=aviro@redhat.com \
--cc=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@chiara.elte.hu \
--cc=riel@conectiva.com.br \
--cc=sct@redhat.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;
as well as URLs for NNTP newsgroup(s).