nfsd4: zero-length WRITE should succeed
authorJ. Bruce Fields <bfields@redhat.com>
Thu, 15 Nov 2018 16:21:40 +0000 (11:21 -0500)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 13 Jan 2019 08:51:08 +0000 (09:51 +0100)
commit3f26e68af5c0a3a0704a44dd0286c785b603a5c8
tree300df8dadeb3a8798177c10bfcb43bec581027e6
parent0b6001b941af35cde42ac3fdd4079488f2f19a82
nfsd4: zero-length WRITE should succeed

commit fdec6114ee1f0f43b1ad081ad8d46b23ba126d70 upstream.

Zero-length writes are legal; from 5661 section 18.32.3: "If the count
is zero, the WRITE will succeed and return a count of zero subject to
permissions checking".

This check is unnecessary and is causing zero-length reads to return
EINVAL.

Cc: stable@vger.kernel.org
Fixes: 3fd9557aec91 "NFSD: Refactor the generic write vector fill helper"
Cc: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/nfsd/nfs4proc.c