From: Jeff Layton <jlayton@redhat.com>
To: trond.myklebust@primarydata.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] nfs4: file locking fixes and cleanups
Date: Wed, 23 Apr 2014 14:24:57 -0400 [thread overview]
Message-ID: <1398277500-31575-1-git-send-email-jlayton@redhat.com> (raw)
The impetus for this set was a bug report in Fedora about "sleeping in
atomic context" warning that patch #2 fixes. While looking at that, I
noticed that a LOCKU wasn't being sent in the reproducer provided so I
tracked down and fixed that bug as well.
These are only lightly tested, and could probably use some soak time in
linux-next. Also, I'm not 100% thrilled with queueing the
free_lock_state job submission to a workqueue, but I don't see a better
way to handle it so far.
Jeff Layton (3):
nfs4: treat lock owners as opaque values
nfs4: queue free_lock_state job submission to nfsiod
nfs4: turn free_lock_state into a void return operation
fs/nfs/nfs4_fs.h | 26 +++++++--------------
fs/nfs/nfs4proc.c | 14 ++++++------
fs/nfs/nfs4state.c | 67 ++++++++++++++++++++++--------------------------------
3 files changed, 42 insertions(+), 65 deletions(-)
--
1.9.0
next reply other threads:[~2014-04-23 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 18:24 Jeff Layton [this message]
2014-04-23 18:24 ` [PATCH 1/3] nfs4: treat lock owners as opaque values Jeff Layton
2014-04-23 18:48 ` Trond Myklebust
2014-04-23 19:00 ` Jeff Layton
2014-04-24 14:25 ` Jeff Layton
2014-04-23 18:24 ` [PATCH 2/3] nfs4: queue free_lock_state job submission to nfsiod Jeff Layton
2014-04-23 18:25 ` [PATCH 3/3] nfs4: turn free_lock_state into a void return operation Jeff Layton
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=1398277500-31575-1-git-send-email-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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;
as well as URLs for NNTP newsgroup(s).