[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.0.999.0710261611511.30120@woody.linux-foundation.org>
Date: Fri, 26 Oct 2007 16:14:10 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Zach Brown <zach.brown@...cle.com>
cc: Karl Schendel <kschendel@...allegro.com>,
Benjamin LaHaise <bcrl@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Nick Piggin <nickpiggin@...oo.com.au>,
Leonid Ananiev <leonid.i.ananiev@...ux.intel.com>,
Chris Mason <chris.mason@...cle.com>
Subject: Re: [PATCH] Fix bad data from non-direct-io read after direct-io
write
On Fri, 26 Oct 2007, Zach Brown wrote:
>
> I can throw together a patch if you haven't already committed one by the
> time you read this ;).
I'm not touching that code except to send out possible patches for others
to test and comment on. I have no test-cases, nor any real interest in it.
So yeah, please send me a tested and thought-through patch.
It sounded like Karl actually had a test-case to trigger this, but maybe
I'm confused (and it sounds a bit unlikely, since it should be hard to
trigger.. Although maybe you can trigger it by doing a direct_IO write
with the *source* being an mmap() of the file you're writing to, and
depending on the write itself re-populating the destination in the page
cache?)
Karl?
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists