Date: Sat, 18 May 2024 19:17:49 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 279138] NFS and NFSUPG and BUFWAIT Message-ID: <bug-279138-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279138 Bug ID: 279138 Summary: NFS and NFSUPG and BUFWAIT Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: dgilbert@eicat.ca Setup: host: 14.0p2, 1900 threadripper (16 threads), 128G ram, 120T zfs vm: 15.0-CURRENT #5 main-n270190-75529910f77a: Thu May 16 19:08:46 EDT 2024 64G ram, 15 processors, 200G ZFS (zvol on host). Host runs poudreiere for <=3D14. VM runs 15 poudriere (not at same time). = VM mounts /usr/local/poudriere via NFS. Multiple times, with at least one make-world on a new pull inbetween, the w= hole things stopps (it didn't used to, 2 to 3 months ago code). Seems to happen when this triple reversal happens: May 17 12:16:24 curpoud kernel: lock order reversal: May 17 12:16:24 curpoud kernel: 1st 0xfffff802dcae0230 nfs (nfs, lockmgr) @ /usr/src/sys/kern/vfs_subr.c:3298 May 17 12:16:24 curpoud kernel: 2nd 0xfffffe006a1633c8 bufwait (bufwait, lockmgr) @ /usr/src/sys/kern/vfs_subr.c:2442 May 17 12:16:24 curpoud kernel: lock order bufwait -> nfs established at: May 17 12:16:24 curpoud kernel: #0 0xffffffff80bb5ca5 at witness_checkorder+0x315 May 17 12:16:24 curpoud kernel: #1 0xffffffff80b0e962 at lockmgr_lock_flags+0x172 May 17 12:16:24 curpoud kernel: #2 0xffffffff80a1990c at nfs_lock+0x2c May 17 12:16:24 curpoud kernel: #3 0xffffffff80c25f50 at vop_sigdefer+0x30 May 17 12:16:24 curpoud kernel: #4 0xffffffff80c52783 at _vn_lock+0x53 May 17 12:16:24 curpoud kernel: #5 0xffffffff80c3a22d at vget_finish+0x4d May 17 12:16:24 curpoud kernel: #6 0xffffffff80c28b91 at vfs_hash_get+0xd1 May 17 12:16:24 curpoud kernel: #7 0xffffffff80a2293b at nfscl_nget+0x13b May 17 12:16:24 curpoud kernel: #8 0xffffffff80a0a2d8 at nfsrpc_readdirplus+0xa98 May 17 12:16:24 curpoud kernel: #9 0xffffffff80a150a0 at ncl_readdirplusrpc+0xf0 May 17 12:16:24 curpoud kernel: #10 0xffffffff80a26cbc at ncl_doio+0x47c May 17 12:16:24 curpoud kernel: #11 0xffffffff80a25e5f at ncl_bioread+0x5ef May 17 12:16:24 curpoud kernel: #12 0xffffffff80a19858 at nfs_readdir+0x1d8 May 17 12:16:24 curpoud kernel: #13 0xffffffff80c25f50 at vop_sigdefer+0x30 May 17 12:16:24 curpoud kernel: #14 0xffffffff811274a2 at VOP_READDIR_APV+0= x32 May 17 12:16:24 curpoud kernel: #15 0xffffffff80c4f05e at kern_getdirentries+0x1ce May 17 12:16:24 curpoud kernel: #16 0xffffffff80c4f459 at sys_getdirentries+0x29 May 17 12:16:24 curpoud kernel: #17 0xffffffff8105f638 at amd64_syscall+0x1= 58 May 17 12:16:24 curpoud kernel: lock order nfs -> bufwait attempted at: May 17 12:16:24 curpoud kernel: #0 0xffffffff80bb650b at witness_checkorder+0xb7b May 17 12:16:24 curpoud kernel: #1 0xffffffff80b0f06e at lockmgr_xlock_hard+0x6e May 17 12:16:24 curpoud kernel: #2 0xffffffff80b0f910 at __lockmgr_args+0x1= e0 May 17 12:16:24 curpoud kernel: #3 0xffffffff80c388e0 at flushbuflist+0x110 May 17 12:16:24 curpoud kernel: #4 0xffffffff80c3859a at bufobj_invalbuf+0x= 8a May 17 12:16:24 curpoud kernel: #5 0xffffffff80a26f20 at ncl_vinvalbuf+0xf0 May 17 12:16:24 curpoud kernel: #6 0xffffffff80a17125 at nfs_open+0x1d5 May 17 12:16:24 curpoud kernel: #7 0xffffffff80c25f50 at vop_sigdefer+0x30 May 17 12:16:24 curpoud kernel: #8 0xffffffff811253cf at VOP_OPEN_APV+0x2f May 17 12:16:24 curpoud kernel: #9 0xffffffff80c52579 at vn_open_vnode+0x1b9 May 17 12:16:24 curpoud kernel: #10 0xffffffff80c51f78 at vn_open_cred+0x598 May 17 12:16:24 curpoud kernel: #11 0xffffffff80c48267 at openatfp+0x287 May 17 12:16:24 curpoud kernel: #12 0xffffffff80c47fbd at sys_openat+0x3d May 17 12:16:24 curpoud kernel: #13 0xffffffff8105f638 at amd64_syscall+0x1= 58 May 17 12:16:24 curpoud kernel: #14 0xffffffff81030cdb at fast_syscall_common+0xf8 May 17 12:16:24 curpoud kernel: lock order reversal: May 17 12:16:24 curpoud kernel: 1st 0xfffffe01c4ec9e60 nfsupg (nfsupg, lockmgr) @ /usr/src/sys/fs/nfsclient/nfs_clsubs.c:151 May 17 12:16:24 curpoud kernel: 2nd 0xfffffe006a174e88 bufwait (bufwait, lockmgr) @ /usr/src/sys/kern/vfs_subr.c:2442 May 17 12:16:24 curpoud kernel: lock order nfsupg -> bufwait attempted at: May 17 12:16:24 curpoud kernel: #0 0xffffffff80bb650b at witness_checkorder+0xb7b May 17 12:16:24 curpoud kernel: #1 0xffffffff80b0f06e at lockmgr_xlock_hard+0x6e May 17 12:16:24 curpoud kernel: #2 0xffffffff80b0f910 at __lockmgr_args+0x1= e0 May 17 12:16:24 curpoud kernel: #3 0xffffffff80c388e0 at flushbuflist+0x110 May 17 12:16:24 curpoud kernel: #4 0xffffffff80c3859a at bufobj_invalbuf+0x= 8a May 17 12:16:24 curpoud kernel: #5 0xffffffff80a26f20 at ncl_vinvalbuf+0xf0 May 17 12:16:24 curpoud kernel: #6 0xffffffff80a25bc8 at ncl_bioread+0x358 May 17 12:16:24 curpoud kernel: #7 0xffffffff80a19858 at nfs_readdir+0x1d8 May 17 12:16:24 curpoud kernel: #8 0xffffffff80c25f50 at vop_sigdefer+0x30 May 17 12:16:24 curpoud kernel: #9 0xffffffff811274a2 at VOP_READDIR_APV+0x= 32 May 17 12:16:24 curpoud kernel: #10 0xffffffff80c4f05e at kern_getdirentries+0x1ce May 17 12:16:24 curpoud kernel: #11 0xffffffff80c4f459 at sys_getdirentries+0x29 May 17 12:16:24 curpoud kernel: #12 0xffffffff8105f638 at amd64_syscall+0x1= 58 May 17 12:16:24 curpoud kernel: #13 0xffffffff81030cdb at fast_syscall_common+0xf8 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279138-227>