From: Dave Wysochanski <dwysocha@redhat.com>
To: Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna.schumaker@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/4] Fix a few error paths in nfs_readpage and fscache
Date: Mon, 28 Jun 2021 13:38:59 -0400 [thread overview]
Message-ID: <1624901943-20027-1-git-send-email-dwysocha@redhat.com> (raw)
A prior patchset refactored some nfs read code paths but introduced a
few problems in some error paths. This patcheset cleans up these
error paths specifically the following commit:
1e83b173b266 ("NFS: Add nfs_pageio_complete_read() and remove nfs_readpage_async()")
The last patch fixes a bug introduced in the above commit, and when
fscache is enabled and an unlikely error occurs. The first 3 patches
are refactorings / cleanups and while they do not fix any actual bug
to my knowledge, they are required for the 4th patch.
NOTE: The first patch was submitted prior as a solo patch[1], it is
included here unchanged from that submission.
[1] https://marc.info/?l=linux-nfs&m=162454885107812&w=2
Testing
=======
I applied this series on top of Trond's testing tree based on 5.13-rc6
and at:
159dd33001be Merge branch 'sysfs-devel'
scripts/checkpatch.pl was run on all patches and no warnings or errors.
For unit tests of these specific code paths I created custom error injection
to induce failures.
For regression, I ran iterations of xfstests with different servers and all NFS
versions (4.2, 4.1, 4.0, 3), including pNFS (flexfiles,filelayout), and
didn't see any new failures.
Dave Wysochanski (4):
NFS: Remove unnecessary inode parameter from
nfs_pageio_complete_read()
NFS: Ensure nfs_readpage does not wait an internal error occurs
NFS: Allow internal use of read structs and functions
NFS: Fix fscache read from NFS after cache error
fs/nfs/fscache.c | 14 ++++++++++++--
fs/nfs/internal.h | 7 +++++++
fs/nfs/read.c | 39 ++++++++++++++++++---------------------
3 files changed, 37 insertions(+), 23 deletions(-)
--
1.8.3.1
next reply other threads:[~2021-06-28 17:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 17:38 Dave Wysochanski [this message]
2021-06-28 17:39 ` [PATCH 1/4] NFS: Remove unnecessary inode parameter from nfs_pageio_complete_read() Dave Wysochanski
2021-06-28 17:39 ` [PATCH 2/4] NFS: Ensure nfs_readpage returns promptly when internal error occurs Dave Wysochanski
2021-06-28 19:17 ` Trond Myklebust
2021-06-28 20:00 ` David Wysochanski
2021-06-28 22:00 ` Trond Myklebust
2021-06-28 17:39 ` [PATCH 3/4] NFS: Allow internal use of read structs and functions Dave Wysochanski
2021-06-28 17:39 ` [PATCH 4/4] NFS: Fix fscache read from NFS after cache error Dave Wysochanski
2021-06-28 19:09 ` Trond Myklebust
2021-06-28 20:15 ` David Wysochanski
2021-06-28 21:12 ` David Wysochanski
2021-06-28 21:59 ` Trond Myklebust
2021-06-28 23:46 ` David Wysochanski
2021-06-29 0:39 ` Trond Myklebust
2021-06-29 9:17 ` David Wysochanski
2021-06-29 12:45 ` Trond Myklebust
2021-06-29 13:20 ` David Wysochanski
2021-06-29 14:54 ` Trond Myklebust
2021-06-29 15:29 ` David Wysochanski
2021-06-29 15:50 ` Trond Myklebust
2021-06-29 15:54 ` Trond Myklebust
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=1624901943-20027-1-git-send-email-dwysocha@redhat.com \
--to=dwysocha@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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