summaryrefslogtreecommitdiffstats
path: root/fs/locks.c
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@redhat.com>2012-08-20 22:04:40 +0200
committerJ. Bruce Fields <bfields@redhat.com>2012-08-21 00:38:59 +0200
commitf06f00a24d76e168ecb38d352126fd203937b601 (patch)
tree14dc65ebb5dc175f68a099f0aaf36b447e1fdcd8 /fs/locks.c
parentsvcrpc: fix BUG() in svc_tcp_clear_pages (diff)
downloadlinux-f06f00a24d76e168ecb38d352126fd203937b601.tar.xz
linux-f06f00a24d76e168ecb38d352126fd203937b601.zip
svcrpc: sends on closed socket should stop immediately
svc_tcp_sendto sets XPT_CLOSE if we fail to transmit the entire reply. However, the XPT_CLOSE won't be acted on immediately. Meanwhile other threads could send further replies before the socket is really shut down. This can manifest as data corruption: for example, if a truncated read reply is followed by another rpc reply, that second reply will look to the client like further read data. Symptoms were data corruption preceded by svc_tcp_sendto logging something like kernel: rpc-srv/tcp: nfsd: sent only 963696 when sending 1048708 bytes - shutting down socket Cc: stable@vger.kernel.org Reported-by: Malahal Naineni <malahal@us.ibm.com> Tested-by: Malahal Naineni <malahal@us.ibm.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/locks.c')
0 files changed, 0 insertions, 0 deletions