Re: NFS panic in latest main

On Tue, Jul 08, 2025 at 09:37:42PM +0200, Dag-Erling Smørgrav wrote:
> With main@72c848089f3b, any attempt by an NFS client to rename a file
> immediately panics the server:
> 
> panic: Lock rename not exclusively locked @ /usr/src/sys/kern/vfs_subr.c:5878
> 
> cpuid = 2
> time = 1752003292
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe008dbd3890
> vpanic() at vpanic+0x136/frame 0xfffffe008dbd39c0
> panic() at panic+0x43/frame 0xfffffe008dbd3a20
> _lockmgr_assert() at _lockmgr_assert+0x12e/frame 0xfffffe008dbd3a30
> vop_rename_pre() at vop_rename_pre+0x12d/frame 0xfffffe008dbd3a70
> VOP_RENAME_APV() at VOP_RENAME_APV+0x23/frame 0xfffffe008dbd3a90
> nfsvno_rename() at nfsvno_rename+0x3b2/frame 0xfffffe008dbd3bc0
> nfsrvd_rename() at nfsrvd_rename+0x5d7/frame 0xfffffe008dbd41c0
> nfsrvd_dorpc() at nfsrvd_dorpc+0x1bc/frame 0xfffffe008dbd43d0
> nfssvc_program() at nfssvc_program+0x852/frame 0xfffffe008dbd45d0
> svc_run_internal() at svc_run_internal+0xaa8/frame 0xfffffe008dbd4700
> svc_run() at svc_run+0x280/frame 0xfffffe008dbd4760
> nfsrvd_nfsd() at nfsrvd_nfsd+0x3d3/frame 0xfffffe008dbd48c0
> nfssvc_nfsd() at nfssvc_nfsd+0x535/frame 0xfffffe008dbd4de0
> sys_nfssvc() at sys_nfssvc+0xcc/frame 0xfffffe008dbd4e00
> amd64_syscall() at amd64_syscall+0x451/frame 0xfffffe008dbd4f30
> fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe008dbd4f30
> --- syscall (155, FreeBSD ELF64, nfssvc), rip = 0x36a11b2334ea, rsp = 0x36a118def0f8, rbp = 0x36a118def390 ---
> KDB: enter: panic
> [ thread pid 3473 tid 100319 ]
> Stopped at      kdb_enter+0x33: movq    $0,0x9a25d2(%rip)
> db> 
> 
> It was fine ~5 days ago.  I have not attempted to bisect.

D51211, I did not tested it.