From: NeilBrown <neilb@suse.com>
To: Jeff Layton <jlayton@redhat.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>
Cc: Benjamin Coddington <bcodding@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/6] NFSv4: Fix stateid used when flock locks in use. - V2
Date: Fri, 18 Nov 2016 15:59:19 +1100 [thread overview]
Message-ID: <878tshfkns.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <8737jtz5nf.fsf@notabene.neil.brown.name>
[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]
Hi all,
what is the status here. I don't see these in linux-next, nor do I see
any issues raise with them.
Is there any chance they can get into 4.10??
Thanks,
NeilBrown
On Wed, Oct 19 2016, NeilBrown wrote:
> [ Unknown signature status ]
> On Fri, Oct 14 2016, Jeff Layton wrote:
>
>>
>> This all looks good to me aside from some minor documentation nits.
>> Kudos too on doing this with a net removal of code. :)
>>
>> Reviewed-by: Jeff Layton <jlayton@redhat.com>
>
> Thanks.
>
> The full series, with Reviewed-by added, is available as below if
> a "git pull" is easier that plucking them out of emails
>
> NeilBrown
>
>
> The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
>
> Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
>
> are available in the git repository at:
>
> git://neil.brown.name/linux tags/nfs-flock-fix
>
> for you to fetch changes up to 077829bfd0e32131b49d87476b69a189e8e13ae8:
>
> NFS: discard nfs_lockowner structure. (2016-10-19 08:44:25 +1100)
>
> ----------------------------------------------------------------
> Series to fix NFSv4 stateid used for flock locks
>
> ----------------------------------------------------------------
> NeilBrown (6):
> NFS: remove l_pid field from nfs_lockowner
> NFSv4: add flock_owner to open context
> NFSv4: change nfs4_do_setattr to take an open_context instead of a nfs4_state.
> NFSv4: change nfs4_select_rw_stateid to take a lock_context inplace of lock_owner
> NFSv4: enhance nfs4_copy_lock_stateid to use a flock stateid if there is one
> NFS: discard nfs_lockowner structure.
>
> fs/nfs/dir.c | 6 +++---
> fs/nfs/inode.c | 14 +++++++-------
> fs/nfs/nfs4_fs.h | 2 +-
> fs/nfs/nfs4file.c | 2 +-
> fs/nfs/nfs4proc.c | 44 +++++++++++++++++++-------------------------
> fs/nfs/nfs4state.c | 49 ++++++++++++++++++++++++++++++++-----------------
> fs/nfs/pagelist.c | 3 +--
> fs/nfs/write.c | 3 +--
> include/linux/nfs_fs.h | 10 +++-------
> 9 files changed, 68 insertions(+), 65 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
prev parent reply other threads:[~2016-11-18 4:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 4:26 [PATCH 0/6] NFSv4: Fix stateid used when flock locks in use. - V2 NeilBrown
2016-10-13 4:26 ` [PATCH 6/6] NFS: discard nfs_lockowner structure NeilBrown
2016-10-13 4:26 ` [PATCH 1/6] NFS: remove l_pid field from nfs_lockowner NeilBrown
2016-10-13 4:26 ` [PATCH 5/6] NFSv4: enhance nfs4_copy_lock_stateid to use a flock stateid if there is one NeilBrown
2016-10-13 15:22 ` Jeff Layton
2016-10-14 0:22 ` NeilBrown
2016-10-14 10:49 ` Jeff Layton
2016-12-19 0:33 ` [PATCH] NFSv4: ensure __nfs4_find_lock_state returns consistent result NeilBrown
2016-10-13 4:26 ` [PATCH 4/6] NFSv4: change nfs4_select_rw_stateid to take a lock_context inplace of lock_owner NeilBrown
2016-10-20 0:57 ` NeilBrown
2016-10-13 4:26 ` [PATCH 2/6] NFSv4: add flock_owner to open context NeilBrown
2016-10-13 4:26 ` [PATCH 3/6] NFSv4: change nfs4_do_setattr to take an open_context instead of a nfs4_state NeilBrown
2016-11-02 15:49 ` Benjamin Coddington
2016-11-02 23:34 ` NeilBrown
2016-11-03 16:38 ` Benjamin Coddington
2016-11-03 23:12 ` Benjamin Coddington
2016-10-13 15:31 ` [PATCH 0/6] NFSv4: Fix stateid used when flock locks in use. - V2 Jeff Layton
2016-10-18 21:52 ` NeilBrown
2016-11-18 4:59 ` NeilBrown [this message]
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=878tshfkns.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=anna.schumaker@netapp.com \
--cc=bcodding@redhat.com \
--cc=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).