android_kernel_xiaomi_sm8350/fs/lockd
Jeff Layton f97c650dda NLM: don't let lockd exit on unexpected svc_recv errors (try #2)
When svc_recv returns an unexpected error, lockd will print a warning
and exit. This problematic for several reasons. In particular, it will
cause the reference counts for the thread to be wrong, and can lead to a
potential BUG() call.

Rather than exiting on error from svc_recv, have the thread do a 1s
sleep and then retry the loop. This is unlikely to cause any harm, and
if the error turns out to be something temporary then it may be able to
recover.

Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
2008-04-23 16:13:43 -04:00
..
clntlock.c NLM: Introduce an arguments structure for nlmclnt_init() 2008-01-30 02:06:07 -05:00
clntproc.c NLM: Fix a bogus 'return' in nlmclnt_rpc_release 2008-01-30 02:06:08 -05:00
host.c lockd: convert nsm_mutex to a spinlock 2008-04-23 16:13:39 -04:00
Makefile
mon.c
svc4proc.c lockd: fix reference count leaks in async locking case 2008-02-01 16:42:06 -05:00
svc.c NLM: don't let lockd exit on unexpected svc_recv errors (try #2) 2008-04-23 16:13:43 -04:00
svclock.c lockd: Fix stale nlmsvc_unlink_block comment 2008-04-23 16:13:42 -04:00
svcproc.c lockd: fix reference count leaks in async locking case 2008-02-01 16:42:06 -05:00
svcshare.c lockd: fix sparse warning in svcshare.c 2008-04-23 16:13:39 -04:00
svcsubs.c lockd: minor log message fix 2008-02-01 16:42:15 -05:00
xdr4.c
xdr.c