diff options
author | rmacklem <rmacklem@FreeBSD.org> | 2016-04-12 20:23:09 +0000 |
---|---|---|
committer | rmacklem <rmacklem@FreeBSD.org> | 2016-04-12 20:23:09 +0000 |
commit | c78bfcfb8f824930b3780c411e7a2031bd719c33 (patch) | |
tree | cf7c12cd4fbf9b2fb823d795afeba814c396a430 /lib/libgssapi/gss_process_context_token.3 | |
parent | 2a0941fb20351d00765ce970ea44efcc0f389e3b (diff) | |
download | FreeBSD-src-c78bfcfb8f824930b3780c411e7a2031bd719c33.zip FreeBSD-src-c78bfcfb8f824930b3780c411e7a2031bd719c33.tar.gz |
If the VOP_SETATTR() call that saves the exclusive create verifier failed,
the NFS server would leave the newly created vnode locked. This could
result in a file system that would not unmount and processes wedged,
waiting for the file to be unlocked.
Since this VOP_SETATTR() never fails for most file systems, this bug
doesn't normally manifest itself. I found it during testing of an
exported GlusterFS file system, which can fail.
This patch adds the vput() and changes the error to the correct NFS one.
MFC after: 2 weeks
Diffstat (limited to 'lib/libgssapi/gss_process_context_token.3')
0 files changed, 0 insertions, 0 deletions