K 10
svn:author
V 8
rmacklem
K 8
svn:date
V 27
2011-06-19T02:24:36.882093Z
K 7
svn:log
V 324
MFC: r222719
The new NFSv4 client was erroneously using "p" instead of
"p_leader" for the "id" for POSIX byte range locking. I think
this would only have affected processes created by rfork(2)
with the RFTHREAD flag specified. This patch fixes that by
passing the "id" down through the various functions from
nfs_advlock().

END