From: Jeff Layton <jeff.layton@primarydata.com>
To: linux-fsdevel@vger.kernel.org
Cc: bfields@fieldses.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] locks: locks related cleanups for v4.1
Date: Sat, 7 Mar 2015 11:09:55 -0500 [thread overview]
Message-ID: <1425744599-4934-1-git-send-email-jeff.layton@primarydata.com> (raw)
Nothing terribly earth-shattering here. Just a few locking-related
cleanup patches that I'm planning to queue up for v4.1. The only one
that really warrants close attention is the 4th one that gets rid of the
i_lock protection around the i_flctx pointer.
One of the earlier patchsets that added the i_flctx field used cmpxchg
to assign it, but I ended up taking that out due to a problem that Sasha
Levin reported. I now think that I misunderstood the problem and that
using cmpxchg for that should be ok.
Jeff Layton (4):
locks: don't allocate a lock context for an F_UNLCK request
locks: change lm_get_owner and lm_put_owner prototypes
locks: get rid of WE_CAN_BREAK_LSLK_NOW dead code
locks: use cmpxchg to assign i_flctx pointer
fs/locks.c | 45 +++++++++++++++++++--------------------------
fs/nfsd/nfs4state.c | 18 ++++++++++--------
include/linux/fs.h | 4 ++--
3 files changed, 31 insertions(+), 36 deletions(-)
--
2.1.0
next reply other threads:[~2015-03-07 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 16:09 Jeff Layton [this message]
2015-03-07 16:09 ` [PATCH 1/4] locks: don't allocate a lock context for an F_UNLCK request Jeff Layton
2015-03-07 16:09 ` [PATCH 2/4] locks: change lm_get_owner and lm_put_owner prototypes Jeff Layton
2015-03-07 16:09 ` [PATCH 3/4] locks: get rid of WE_CAN_BREAK_LSLK_NOW dead code Jeff Layton
2015-03-07 16:09 ` [PATCH 4/4] locks: use cmpxchg to assign i_flctx pointer 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=1425744599-4934-1-git-send-email-jeff.layton@primarydata.com \
--to=jeff.layton@primarydata.com \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
Powered by JetHome