summaryrefslogtreecommitdiffstats
path: root/lib/libmemstat/memstat_malloc.c
diff options
context:
space:
mode:
authorrmacklem <rmacklem@FreeBSD.org>2011-07-31 20:06:11 +0000
committerrmacklem <rmacklem@FreeBSD.org>2011-07-31 20:06:11 +0000
commited9d50749cb2eceeab3a84829fc923e9d8fe3dff (patch)
tree64b258571353c719519c6df66155fcac7f87d9d6 /lib/libmemstat/memstat_malloc.c
parente9752126de05c72ff44f9f9a487d8f2d1b8c8f40 (diff)
downloadFreeBSD-src-ed9d50749cb2eceeab3a84829fc923e9d8fe3dff.zip
FreeBSD-src-ed9d50749cb2eceeab3a84829fc923e9d8fe3dff.tar.gz
Fix rename in the new NFS server so that it does not require a
recursive vnode lock on the directory for the case where the new file name is in the same directory as the old one. The patch handles this as a special case, recognized by the new directory having the same file handle as the old one and just VREF()s the old dir vnode for this case, instead of doing a second VFS_FHTOVP() to get it. This is required so that the server will work for file systems like msdosfs, that do not support recursive vnode locking. This problem was discovered during recent testing by pho@ when exporting an msdosfs file system via the new NFS server. Tested by: pho Reviewed by: zkirsch Approved by: re (kib) MFC after: 2 weeks
Diffstat (limited to 'lib/libmemstat/memstat_malloc.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud