From: Jeff Layton <jlayton@primarydata.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] nfsd: fi_delegees bugfix and cleanup
Date: Sat, 13 Dec 2014 09:11:38 -0500 [thread overview]
Message-ID: <1418479900-4757-1-git-send-email-jlayton@primarydata.com> (raw)
Hi Bruce,
As I mentioned on IRC yesterday, here are a couple of patches to the
fi_delegees handling. The first one fixes a bug. I think it's pretty
unlikely to be hit in most cases, so I'm not sure if it's suitable for
stable. Your call there.
The second is just a cleanup patch -- fi_delegees is always handled
under spinlock so it really doesn't need to be an atomic_t.
Jeff Layton (2):
nfsd: fix fi_delegees leak when fi_had_conflict returns true
nfsd: fi_delegees doesn't need to be an atomic_t
fs/nfsd/nfs4state.c | 8 ++++----
fs/nfsd/state.h | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
--
2.1.0
next reply other threads:[~2014-12-13 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 14:11 Jeff Layton [this message]
2014-12-13 14:11 ` [PATCH 1/2] nfsd: fix fi_delegees leak when fi_had_conflict returns true Jeff Layton
2014-12-13 14:11 ` [PATCH 2/2] nfsd: fi_delegees doesn't need to be an atomic_t Jeff Layton
2014-12-17 19:01 ` [PATCH 0/2] nfsd: fi_delegees bugfix and cleanup J. Bruce Fields
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=1418479900-4757-1-git-send-email-jlayton@primarydata.com \
--to=jlayton@primarydata.com \
--cc=bfields@fieldses.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