NFSv4.2 copy do not allocate memory under the lock
authorOlga Kornievskaia <kolga@netapp.com>
Wed, 21 Nov 2018 16:24:22 +0000 (11:24 -0500)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 13 Dec 2018 08:16:14 +0000 (09:16 +0100)
commit07b92c224d5ca13aa07dd1c31908dfa19400df3e
tree156c7b5977adc0dffb9fe7517cad35d2ecd5eb36
parentd1862827f41a79560bb98ba91e6b4be8f8c726f9
NFSv4.2 copy do not allocate memory under the lock

[ Upstream commit 99f2c55591fb5c1b536263970d98c2ebc2089906 ]

Bruce pointed out that we shouldn't allocate memory while holding
a lock in the nfs4_callback_offload() and handle_async_copy()
that deal with a racing CB_OFFLOAD and reply to COPY case.

Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/nfs/callback_proc.c
fs/nfs/nfs42proc.c