From: Benjamin Coddington <bcodding@redhat.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Jeff Layton <jlayton@poochiereds.net>,
bfields@fieldses.org
Cc: linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] Fixups for l_pid
Date: Fri, 26 May 2017 16:14:48 -0400 [thread overview]
Message-ID: <cover.1495829587.git.bcodding@redhat.com> (raw)
LTP fcntl tests (fcntl11 fcntl14 fcntl17 fcntl19 fcntl20 fcntl21) have been
failing for NFSv4 mounts due to an unexpected l_pid. What follows are some
fixups:
Benjamin Coddington (3):
fs/locks: Alloc file_lock where practical
fs/locks: Set fl_nspid at file_lock allocation
fs/locks: Use fs-specific l_pid for remote locks
fs/locks.c | 137 +++++++++++++++++++++++++++++++++--------------------
include/linux/fs.h | 1 +
2 files changed, 86 insertions(+), 52 deletions(-)
--
2.9.3
next reply other threads:[~2017-05-26 20:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 20:14 Benjamin Coddington [this message]
2017-05-26 20:14 ` [PATCH 1/3] fs/locks: Alloc file_lock where practical Benjamin Coddington
2017-05-27 9:56 ` Jeff Layton
2017-05-28 6:35 ` Christoph Hellwig
2017-05-26 20:14 ` [PATCH 2/3] fs/locks: Set fl_nspid at file_lock allocation Benjamin Coddington
2017-05-27 10:00 ` Jeff Layton
2017-06-01 2:05 ` [lkp-robot] [fs/locks] 9d21d181d0: will-it-scale.per_process_ops -14.1% regression kernel test robot
2017-06-01 11:41 ` Jeff Layton
2017-06-01 11:41 ` Jeff Layton
2017-06-01 11:49 ` Benjamin Coddington
2017-06-01 11:49 ` Benjamin Coddington
2017-06-01 12:59 ` Jeff Layton
2017-06-01 12:59 ` Jeff Layton
2017-06-01 15:14 ` J. Bruce Fields
2017-06-01 15:48 ` Jeff Layton
2017-06-01 15:48 ` Jeff Layton
2017-06-05 18:34 ` Benjamin Coddington
2017-06-05 18:34 ` Benjamin Coddington
2017-06-05 22:02 ` Jeff Layton
2017-06-05 22:02 ` Jeff Layton
2017-06-06 13:00 ` Benjamin Coddington
2017-06-06 13:00 ` Benjamin Coddington
2017-06-06 13:15 ` Jeff Layton
2017-06-06 13:15 ` Jeff Layton
2017-06-06 13:21 ` Benjamin Coddington
2017-06-06 13:21 ` Benjamin Coddington
2017-05-26 20:14 ` [PATCH 3/3] fs/locks: Use fs-specific l_pid for remote locks Benjamin Coddington
2017-05-26 20:26 ` [PATCH 0/3] Fixups for l_pid Benjamin Coddington
2017-05-27 10:11 ` 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=cover.1495829587.git.bcodding@redhat.com \
--to=bcodding@redhat.com \
--cc=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.