From: Nick Piggin <npiggin@suse.de>
To: David Chinner <dgc@sgi.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Hugh Dickins <hugh@veritas.com>, Andrew Morton <akpm@osdl.org>,
Linux Memory Management <linux-mm@kvack.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Filesystems <linux-fsdevel@vger.kernel.org>
Subject: Re: [patch 0/3] 2.6.20 fix for PageUptodate memorder problem
Date: Wed, 7 Feb 2007 04:13:04 +0100 [thread overview]
Message-ID: <20070207031304.GB31074@wotan.suse.de> (raw)
In-Reply-To: <20070206225857.GV44411608@melbourne.sgi.com>
On Wed, Feb 07, 2007 at 09:58:57AM +1100, David Chinner wrote:
> On Tue, Feb 06, 2007 at 09:02:01AM +0100, Nick Piggin wrote:
> > Still no independent confirmation as to whether this is a problem or not.
> > I think it is, so I'll propose this patchset to fix it. Patch 1/3 has a
> > reasonable description of the problem.
> >
>
> Nick, can you include a diffstat at the head of your patches? Makes
> it much easier to see what the scope of the changes are when you
> are changing code in several filesystems....
Good idea, I'll do that.
Thanks,
Nick
prev parent reply other threads:[~2007-02-07 3:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 8:02 [patch 0/3] 2.6.20 fix for PageUptodate memorder problem Nick Piggin
2007-02-06 8:02 ` [patch 1/3] mm: fix PageUptodate memorder Nick Piggin
2007-02-06 8:25 ` Andrew Morton
2007-02-06 8:51 ` Nick Piggin
2007-02-06 8:02 ` [patch 2/3] fs: buffer don't PageUptodate without page locked Nick Piggin
2007-02-06 8:21 ` Andrew Morton
2007-02-06 8:31 ` Nick Piggin
2007-02-06 8:02 ` [patch 3/3] mm: make read_cache_page synchronous Nick Piggin
2007-02-06 8:28 ` Andrew Morton
2007-02-06 8:56 ` Nick Piggin
2007-02-06 8:58 ` Nick Piggin
2007-02-06 22:58 ` [patch 0/3] 2.6.20 fix for PageUptodate memorder problem David Chinner
2007-02-07 3:13 ` Nick Piggin [this message]
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=20070207031304.GB31074@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@osdl.org \
--cc=dgc@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
/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).