From: trondmy@kernel.org
To: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] Don't do pNFS I/O when not holding a layout
Date: Wed, 5 Aug 2020 16:24:29 -0400 [thread overview]
Message-ID: <20200805202431.627013-1-trondmy@kernel.org> (raw)
From: Trond Myklebust <trond.myklebust@hammerspace.com>
We recently discovered a couple of issues in the pNFS client that can
cause it to return a layout while some of the layout segments being
returned are still in use for I/O.
The following 2 patches will add appropriate tests to ensure this
cannot happen, and that the layoutreturn call is delayed until
the outstanding I/O is finished.
Trond Myklebust (2):
NFS: Don't move layouts to plh_return_segs list while in use
NFS: Don't return layout segments that are in use
fs/nfs/pnfs.c | 46 ++++++++++++++++------------------------------
1 file changed, 16 insertions(+), 30 deletions(-)
--
2.26.2
next reply other threads:[~2020-08-05 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 20:24 trondmy [this message]
2020-08-05 20:24 ` [PATCH 1/2] NFS: Don't move layouts to plh_return_segs list while in use trondmy
2020-08-05 20:24 ` [PATCH 2/2] NFS: Don't return layout segments that are " trondmy
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=20200805202431.627013-1-trondmy@kernel.org \
--to=trondmy@kernel.org \
--cc=linux-nfs@vger.kernel.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