From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"dhowells@redhat.com" <dhowells@redhat.com>
Cc: "cmaiolino@redhat.com" <cmaiolino@redhat.com>,
"carmark.dlut@gmail.com" <carmark.dlut@gmail.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-cachefs@redhat.com" <linux-cachefs@redhat.com>,
"dwysocha@redhat.com" <dwysocha@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>
Subject: Re: [PATCH 0/5] cachefiles, nfs: Fixes
Date: Sun, 10 May 2020 13:39:03 +0000 [thread overview]
Message-ID: <d4efead1d6dba67f5c862a8d00ca88dd3c45dd34.camel@hammerspace.com> (raw)
In-Reply-To: <158897619675.1119820.2203023452686054109.stgit@warthog.procyon.org.uk>
Hi David,
On Fri, 2020-05-08 at 23:16 +0100, David Howells wrote:
> Hi Linus, Trond, Anna,
>
> Can you pull these fixes for cachefiles and NFS's use of
> fscache? Should
> they go through the NFS tree or directly upstream? The things fixed
> are:
>
> (1) The reorganisation of bmap() use accidentally caused the return
> value
> of cachefiles_read_or_alloc_pages() to get corrupted.
>
> (2) The NFS superblock index key accidentally got changed to include
> a
> number of kernel pointers - meaning that the key isn't matchable
> after
> a reboot.
>
> (3) A redundant check in nfs_fscache_get_super_cookie().
>
> (4) The NFS change_attr sometimes set in the auxiliary data for the
> caching of an file and sometimes not, which causes the cache to
> get
> discarded when it shouldn't.
>
> (5) There's a race between cachefiles_read_waiter() and
> cachefiles_read_copier() that causes an occasional assertion
> failure.
>
> The patches are tagged here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-
> fs.git
> tag fscache-fixes-20200508-2
>
> Thanks,
> David
> ---
> Dave Wysochanski (3):
> NFS: Fix fscache super_cookie index_key from changing after
> umount
> NFS: Fix fscache super_cookie allocation
> NFSv4: Fix fscache cookie aux_data to ensure change_attr is
> included
>
> David Howells (1):
> cachefiles: Fix corruption of the return value in
> cachefiles_read_or_alloc_pages()
>
> Lei Xue (1):
> cachefiles: Fix race between read_waiter and read_copier
> involving op->to_do
>
>
> fs/cachefiles/rdwr.c | 12 ++++++------
> fs/nfs/fscache.c | 39 ++++++++++++++++++---------------------
> fs/nfs/super.c | 1 -
> 3 files changed, 24 insertions(+), 28 deletions(-)
>
I can pull this branch, and send it together with the NFS client
bugfixes for 5.7-rc5.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2020-05-10 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 22:16 [PATCH 0/5] cachefiles, nfs: Fixes David Howells
2020-05-08 22:16 ` [PATCH 1/5] cachefiles: Fix corruption of the return value in cachefiles_read_or_alloc_pages() David Howells
2020-05-08 22:17 ` [PATCH 2/5] NFS: Fix fscache super_cookie index_key from changing after umount David Howells
2020-05-08 22:17 ` [PATCH 3/5] NFS: Fix fscache super_cookie allocation David Howells
2020-05-08 22:17 ` [PATCH 4/5] NFSv4: Fix fscache cookie aux_data to ensure change_attr is included David Howells
2020-05-08 22:17 ` [PATCH 5/5] cachefiles: Fix race between read_waiter and read_copier involving op->to_do David Howells
2020-05-10 13:39 ` Trond Myklebust [this message]
2020-05-10 20:35 ` [PATCH 0/5] cachefiles, nfs: Fixes David Howells
2020-05-11 22:38 ` NeilBrown
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=d4efead1d6dba67f5c862a8d00ca88dd3c45dd34.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=anna.schumaker@netapp.com \
--cc=carmark.dlut@gmail.com \
--cc=cmaiolino@redhat.com \
--cc=dhowells@redhat.com \
--cc=dwysocha@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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).