aboutsummaryrefslogtreecommitdiff
path: root/arch/mips/cavium-octeon/crypto/octeon-sha1.c
diff options
context:
space:
mode:
authorDavid Howells <dhowells@redhat.com>2019-11-19 21:00:36 +0000
committerLinus Torvalds <torvalds@linux-foundation.org>2019-11-19 14:36:38 -0800
commitc74386d50fbaf4a54fd3fe560f1abc709c0cff4b (patch)
tree97ba35745fa3584d8a6d29c7dd13e5dd9a487ea9 /arch/mips/cavium-octeon/crypto/octeon-sha1.c
parentfd8f64df95204951c3edd4c4a7817c909d55a100 (diff)
downloadlinux-master.tar.gz
afs: Fix missing timeout resetHEADmaster
In afs_wait_for_call_to_complete(), rather than immediately aborting an operation if a signal occurs, the code attempts to wait for it to complete, using a schedule timeout of 2*RTT (or min 2 jiffies) and a check that we're still receiving relevant packets from the server before we consider aborting the call. We may even ping the server to check on the status of the call. However, there's a missing timeout reset in the event that we do actually get a packet to process, such that if we then get a couple of short stalls, we then time out when progress is actually being made. Fix this by resetting the timeout any time we get something to process. If it's the failure of the call then the call state will get changed and we'll exit the loop shortly thereafter. A symptom of this is data fetches and stores failing with EINTR when they really shouldn't. Fixes: bc5e3a546d55 ("rxrpc: Use MSG_WAITALL to tell sendmsg() to temporarily ignore signals") Signed-off-by: David Howells <dhowells@redhat.com> Reviewed-by: Marc Dionne <marc.dionne@auristor.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/mips/cavium-octeon/crypto/octeon-sha1.c')
0 files changed, 0 insertions, 0 deletions