On Sun, 5 Jun 2011, Rick Macklem wrote:
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
Author: rmacklem
Date: Sun Jun 5 18:17:37 2011
New Revision: 222719
URL: http://svn.freebsd.org/changeset/base/222719
Log:
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
