From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Benjamin Coddington <bcodding@redhat.com>,
Anna Schumaker <anna.schumaker@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v3 0/2] Fix OPEN/CLOSE races
Date: Fri, 27 Oct 2017 16:18:27 -0400 [thread overview]
Message-ID: <20171027201829.98702-1-trond.myklebust@primarydata.com> (raw)
Patches to fix up the race between OPEN and CLOSE.
v2:
- Fix a sleep-while-atomic issue
- Clean up.
- Add a tracepoint to help document wait incidents.
v3:
- Fix a state update issue
Trond Myklebust (2):
NFSv4: Fix OPEN / CLOSE race
NFSv4: Add a tracepoint to document open stateid updates
fs/nfs/nfs4_fs.h | 1 +
fs/nfs/nfs4proc.c | 135 +++++++++++++++++++++++++++++++++++++++++------------
fs/nfs/nfs4trace.h | 2 +
3 files changed, 109 insertions(+), 29 deletions(-)
--
2.13.6
next reply other threads:[~2017-10-27 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 20:18 Trond Myklebust [this message]
2017-10-27 20:18 ` [PATCH v3 1/2] NFSv4: Fix OPEN / CLOSE race Trond Myklebust
2017-10-27 20:18 ` [PATCH v3 2/2] NFSv4: Add a tracepoint to document open stateid updates Trond Myklebust
2017-10-30 18:32 ` [PATCH v3 0/2] Fix OPEN/CLOSE races 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=20171027201829.98702-1-trond.myklebust@primarydata.com \
--to=trond.myklebust@primarydata.com \
--cc=anna.schumaker@netapp.com \
--cc=bcodding@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).