summaryrefslogtreecommitdiffstats
path: root/sys/kern/kern_umtx.c
diff options
context:
space:
mode:
authorrmacklem <rmacklem@FreeBSD.org>2011-12-03 02:27:26 +0000
committerrmacklem <rmacklem@FreeBSD.org>2011-12-03 02:27:26 +0000
commitec04bcd39d758acbc7e7de9b331c847bfbe6b8c5 (patch)
tree290697be20f4ccdfbfcdddbdc5806b87bf4a7a5a /sys/kern/kern_umtx.c
parentc1dda66820c6e6eccf0746ee8557255b2cf4ab80 (diff)
downloadFreeBSD-src-ec04bcd39d758acbc7e7de9b331c847bfbe6b8c5.zip
FreeBSD-src-ec04bcd39d758acbc7e7de9b331c847bfbe6b8c5.tar.gz
Post r223774, the NFSv4 client no longer has multiple instances
of the same lock_owner4 string. As such, the handling of cleanup of lock_owners could be simplified. This simplification permitted the client to do a ReleaseLockOwner operation when the process that the lock_owner4 string represents, has exited. This permits the server to release any storage related to the lock_owner4 string before the associated open is closed. Without this change, it is possible to exhaust a server's storage when a long running process opens a file and then many child processes do locking on the file, because the open doesn't get closed. A similar patch was applied to the Linux NFSv4 client recently so that it wouldn't exhaust a server's storage. Reviewed by: zack MFC after: 2 weeks
Diffstat (limited to 'sys/kern/kern_umtx.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud