aboutsummaryrefslogtreecommitdiffstats
path: root/net/unix/af_unix.c
diff options
context:
space:
mode:
authorChuck Lever <[email protected]>2019-11-05 16:04:13 +0000
committerTrond Myklebust <[email protected]>2019-11-18 10:04:32 +0000
commit21f86d2d63f9b0c10a3bd369ce8c97f1f786be53 (patch)
treee3984e7e2e7c4e0265525b6888093f6de83a1caa /net/unix/af_unix.c
parentNFS4: Trace state recovery operation (diff)
downloadkernel-21f86d2d63f9b0c10a3bd369ce8c97f1f786be53.tar.gz
kernel-21f86d2d63f9b0c10a3bd369ce8c97f1f786be53.zip
NFS4: Trace lock reclaims
One of the most frustrating messages our sustaining team sees is the "Lock reclaim failed!" message. Add some observability in the client's lock reclaim logic so we can capture better data the first time a problem occurs. Signed-off-by: Chuck Lever <[email protected]> Signed-off-by: Trond Myklebust <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions