summaryrefslogtreecommitdiffstats
path: root/contrib/llvm/tools/clang/lib
diff options
context:
space:
mode:
authorrmacklem <rmacklem@FreeBSD.org>2011-06-05 18:17:37 +0000
committerrmacklem <rmacklem@FreeBSD.org>2011-06-05 18:17:37 +0000
commit89d4f3434da83d57cf39b1eeaa97a02ec12808ce (patch)
tree35b381de51f06dd88e54c67bb67b2d8a156bf014 /contrib/llvm/tools/clang/lib
parentc16b5c2bd2ccc68700c5e0c73a0b073be9c7b44f (diff)
downloadFreeBSD-src-89d4f3434da83d57cf39b1eeaa97a02ec12808ce.zip
FreeBSD-src-89d4f3434da83d57cf39b1eeaa97a02ec12808ce.tar.gz
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
Diffstat (limited to 'contrib/llvm/tools/clang/lib')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud