Re: [PATCH 0/4] Properly invalidate data in the cleancache.

2017-04-18 Thread Konrad Rzeszutek Wilk
On Fri, Apr 14, 2017 at 05:07:49PM +0300, Andrey Ryabinin wrote: > We've noticed that after direct IO write, buffered read sometimes gets > stale data which is coming from the cleancache. That is not good. > The reason for this is that some direct write hooks call call >

Re: [PATCH 0/4] Properly invalidate data in the cleancache.

2017-04-18 Thread Konrad Rzeszutek Wilk
On Fri, Apr 14, 2017 at 05:07:49PM +0300, Andrey Ryabinin wrote: > We've noticed that after direct IO write, buffered read sometimes gets > stale data which is coming from the cleancache. That is not good. > The reason for this is that some direct write hooks call call >

[PATCH 0/4] Properly invalidate data in the cleancache.

2017-04-14 Thread Andrey Ryabinin
We've noticed that after direct IO write, buffered read sometimes gets stale data which is coming from the cleancache. The reason for this is that some direct write hooks call call invalidate_inode_pages2[_range]() conditionally iff mapping->nrpages is not zero, so we may not invalidate data in

[PATCH 0/4] Properly invalidate data in the cleancache.

2017-04-14 Thread Andrey Ryabinin
We've noticed that after direct IO write, buffered read sometimes gets stale data which is coming from the cleancache. The reason for this is that some direct write hooks call call invalidate_inode_pages2[_range]() conditionally iff mapping->nrpages is not zero, so we may not invalidate data in