rmacklem 89d4f3434d 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().

MFC after:	2 weeks
2011-06-05 18:17:37 +00:00
..
2011-06-02 09:56:42 +00:00
2011-05-22 09:58:48 +00:00
2011-06-05 11:40:30 +00:00
2011-06-02 09:56:53 +00:00