Vinícius Ferrão has uploaded this change for review.
LOCK: describe the conflict in the reply to a blocked lock (#1430)
A blocking LOCK that meets a conflict is answered NFS4ERR_DENIED, but
the conflict is never copied, so the reply carries uninitialised stack
memory as its offset, length and type. In a capture of cthon04's lock
test 7, the length was a heap address. Copy the conflict, or send the
requested range when there is none, as RFC 8881 18.10.4 asks.
GitHub Issue: #1430
Change-Id: I6dbd1588abac2bdec7671cfc461fdeaf88970fa2
Signed-off-by: Vinícius Ferrão <ferrao@versatushpc.com.br>
---
M src/Protocols/NFS/nfs4_op_lock.c
M src/SAL/state_lock.c
2 files changed, 9 insertions(+), 0 deletions(-)
git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/73/1255673/1
To view, visit change 1255673. To unsubscribe, or for help writing mail filters, visit settings.