From: "Stephen C. Tweedie" <sct@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alexander Viro <viro@math.psu.edu>,
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: Tue, 5 Dec 2000 17:09:50 +0000 [thread overview]
Message-ID: <20001205170950.D10663@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0012042232220.7166-100000@weyl.math.psu.edu> <Pine.LNX.4.10.10012041955000.860-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10012041955000.860-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Mon, Dec 04, 2000 at 08:00:03PM -0800
Hi,
On Mon, Dec 04, 2000 at 08:00:03PM -0800, Linus Torvalds wrote:
>
> On Mon, 4 Dec 2000, Alexander Viro wrote:
> >
> 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);
That is still buggy. We MUST NOT invalidate the inode buffers unless
i_nlink == 0, because otherwise a subsequent open() and fsync() will
have forgotten what buffers are dirty, and hence will fail to
synchronise properly with the disk.
Al, I agreed with your observation on bforget() needing the
remove_inode_queue() call. Is there anywhere else we need it?
--Stephen
-
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 17:43 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 ` test12-pre5 Linus Torvalds
2000-12-05 4:25 ` test12-pre5 Alexander Viro
2000-12-05 17:09 ` Stephen C. Tweedie [this message]
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-06 10:05 ` Trond Myklebust
2000-12-10 13:43 ` Urban Widmark
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=20001205170950.D10663@redhat.com \
--to=sct@redhat.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=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 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.