[PATCH] fs: make sure to invalidate pages if we fall back on buffered reads

Since BTRFS can fallback on buffered reads after having done some direct reads, we need to make sure to invalidate any pages that we may have read by doing buffered IO. This shouldn't have shown up as a visible user problem, it's just for correctness sake. Thanks, Signed-off-by: Josef Bacik ---

Re: [PATCH] fs: make sure to invalidate pages if we fall back on buffered reads

Josef Bacik writes: > Since BTRFS can fallback on buffered reads after having done some direct > reads, > we need to make sure to invalidate any pages that we may have read by doing > buffered IO. This shouldn't have shown up as a visible user problem, it's > just > for correctness sake. Than

Re: [PATCH] fs: make sure to invalidate pages if we fall back on buffered reads

On Tue, Jun 08, 2010 at 10:24:04AM -0400, Josef Bacik wrote: > Since BTRFS can fallback on buffered reads after having done some direct > reads, > we need to make sure to invalidate any pages that we may have read by doing > buffered IO. This shouldn't have shown up as a visible user problem, it'

Re: [PATCH] fs: make sure to invalidate pages if we fall back on buffered reads

On Mon, Jun 14, 2010 at 04:17:36AM -0400, Christoph Hellwig wrote: > On Tue, Jun 08, 2010 at 10:24:04AM -0400, Josef Bacik wrote: > > Since BTRFS can fallback on buffered reads after having done some direct > > reads, > > we need to make sure to invalidate any pages that we may have read by doing