Re: NFSD threads hang when destroying a session or client ID

Chuck Lever via Bugspray Bot
2025-01-29T19:49:41Z

Chuck Lever writes via Kernel.org Bugzilla:

Looking further back in trace.dat:

kworker/u194:9-1629754 [033] 309447.521022: nfsd_cb_free_slot: task:00001fa3@0000009a sessionid=67952a7d:4dd6ab1d:00000fb0:00000000 new slot seqno=8100
kworker/u193:6-1630755 [004] 309468.053064: nfsd_cb_seq_status: task:00001fa4@0000009a sessionid=67952a7d:4dd6ab1d:00000fb0:00000000 tk_status=0 seq_status=0
kworker/u193:6-1630755 [004] 309468.053066: nfsd_cb_free_slot: task:00001fa4@0000009a sessionid=67952a7d:4dd6ab1d:00000fb0:00000000 new slot seqno=8101
kworker/u194:13-1634037 [013] 309549.519294: nfsd_cb_seq_status: task:00001fa5@0000009a sessionid=67952a7d:4dd6ab1d:00000fb0:00000000 tk_status=-5 seq_status=1
kworker/u194:13-1634037 [037] 309558.734930: nfsd_cb_seq_status: task:00001fa6@0000009a sessionid=67952a7d:4dd6ab1d:00000fb0:00000000 tk_status=-5 seq_status=1
kworker/u194:0-1662968 [047] 309567.950612: nfsd_cb_seq_status: task:00001fa7@0000009a sessionid=67952a7d:4dd6ab1d:00000fb0:00000000 tk_status=-5 seq_status=1
kworker/u194:13-1634037 [043] 309577.167133: nfsd_cb_seq_status: task:00001fa8@0000009a sessionid=67952a7d:4dd6ab1d:00000fb0:00000000 tk_status=-5 seq_status=1
kworker/u193:14-1658519 [008] 309586.381715: nfsd_cb_seq_status: task:00001fa9@0000009a sessionid=67952a7d:4dd6ab1d:00000fb0:00000000 tk_status=-5 seq_status=1
kworker/u194:6-1659115 [045] 309588.599171: nfsd_cb_seq_status: task:00001faa@0000009a sessionid=67952a7d:4dd6ab1d:00000fb0:00000000 tk_status=-512 seq_status=1

(Not shown here) this is a CB_RECALL_ANY operation that was sent several times but timed out. The retry mechanism could have dropped this operation after the first timeout, or it could have noticed that the callback transport was marked FAULT.

This situation appears to resolve itself.

View: https://bugzilla.kernel.org/show_bug.cgi?id=219710#c26