[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-cifs
Subject:    Re: [PATCH v2 0/4] cifs: cache invalidation fixes when cache=loose
From:       Steve French <smfrench () gmail ! com>
Date:       2014-05-12 4:09:07
Message-ID: CAH2r5mvzhDc-Ndh5AMHHk0n=r2g80v+7mFVOYYf8Wr58mzN_aA () mail ! gmail ! com
[Download RAW message or body]

series merged into cifs-2.6.git for-next

On Wed, Apr 30, 2014 at 8:31 AM, Jeff Layton <jlayton@poochiereds.net> wrote:
> This is the second posting of this patchset. The end result of this set
> should be indentical to the v1 set, but this fixes some problems in the
> intermediate changes that would have introduced bugs for someone doing
> a bisect.
>
> This patchset fixes up some cache invalidation problems that can occur
> when cache=loose. The main point is to ensure that we revalidate the
> cache prior to satisfying a read.
>
> At the same time, I added a fix for a potential problem that cropped up
> with NFS a while back, and to which CIFS is also vulnerable.
>
> This was originally reported by Tetsuo Handa, and as far as I can tell
> this fixes his testcase, assuming that you also ensure that kernel
> oplocks are enabled.
>
> Given that we're late in the cycle, I'd like to see these merged for
> v3.16 but getting them into -next soon would be good.
>
> Jeff Layton (4):
>   cifs: convert booleans in cifsInodeInfo to a flags field
>   cifs: new helper function: cifs_revalidate_mapping
>   cifs: fix potential races in cifs_revalidate_mapping
>   cifs: revalidate mapping prior to satisfying aio_read request
>
>  fs/cifs/cifsfs.c   | 24 ++++++++++++------
>  fs/cifs/cifsfs.h   |  2 ++
>  fs/cifs/cifsglob.h |  7 +++---
>  fs/cifs/file.c     | 16 ++++++------
>  fs/cifs/inode.c    | 71 ++++++++++++++++++++++++++++++++++++++++++------------
>  5 files changed, 86 insertions(+), 34 deletions(-)
>
> --
> 1.9.0
>



-- 
Thanks,

Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]