summaryrefslogtreecommitdiffstats
path: root/contrib/netbsd-tests/lib/libc
diff options
context:
space:
mode:
authorrmacklem <rmacklem@FreeBSD.org>2016-05-06 23:44:24 +0000
committerrmacklem <rmacklem@FreeBSD.org>2016-05-06 23:44:24 +0000
commit45f14820b0ec21c50e7647c5dfde71d497adade8 (patch)
tree3592e4e36007bf736cb267ad71b631cca20c3fae /contrib/netbsd-tests/lib/libc
parent00649b2ea81b97c73999ace6219ec79a366790a2 (diff)
downloadFreeBSD-src-45f14820b0ec21c50e7647c5dfde71d497adade8.zip
FreeBSD-src-45f14820b0ec21c50e7647c5dfde71d497adade8.tar.gz
MFC: r297837
Bruce Evans reported that there was a performance regression between the old and new NFS clients. He did a good job of isolating the problem which was caused by the new NFS client not setting the post write mtime correctly. The new NFS client code was cloned from the old client, but was incorrect, because the mtime in the nfs vnode's cache wasn't yet updated. This patch fixes this problem. The patch also adds missing mutex locking.
Diffstat (limited to 'contrib/netbsd-tests/lib/libc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud