aboutsummaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorNeilBrown <[email protected]>2016-10-13 15:26:47 +1100
committerTrond Myklebust <[email protected]>2016-12-01 17:57:07 -0500
commitb184b5c38e4640585126e44ef84f2dbdd0d23d5a (patch)
tree25de3c489b02736f94b4625797bd7850bdc3947f /include/linux
parent4d3b55d3c7c8c628498fefac4779fc02de5af492 (diff)
NFS: remove l_pid field from nfs_lockowner
this field is not used in any important way and probably should have been removed by Commit: 8003d3c4aaa5 ("nfs4: treat lock owners as opaque values") which removed the pid argument from nfs4_get_lock_state. Except in unusual and uninteresting cases, two threads with the same ->tgid will have the same ->files pointer, so keeping them both for comparison brings no benefit. Acked-by: Jeff Layton <[email protected]> Signed-off-by: NeilBrown <[email protected]> Reviewed-by: Jeff Layton <[email protected]> Signed-off-by: Trond Myklebust <[email protected]>
Diffstat (limited to 'include/linux')
-rw-r--r--include/linux/nfs_fs.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/linux/nfs_fs.h b/include/linux/nfs_fs.h
index 810124b33327..bf8a713c45b4 100644
--- a/include/linux/nfs_fs.h
+++ b/include/linux/nfs_fs.h
@@ -57,7 +57,6 @@ struct nfs_access_entry {
struct nfs_lockowner {
fl_owner_t l_owner;
- pid_t l_pid;
};
struct nfs_lock_context {