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@xxxxxxxxxx> > > 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:
signature.asc
Description: PGP signature
