Date: Sun, 20 Oct 2024 15:17:29 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 282169] zfs rename deadlock with mountd, df & fstat (and possibly others) Message-ID: <bug-282169-3630-ObgPitkSmF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-282169-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-282169-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282169 --- Comment #2 from Mark Johnston <markj@FreeBSD.org> --- (In reply to Mark Johnston from comment #1) ah, I missed the comment at the top of the function. The caller is expecte= d to call zfs_resume_fs() to release the locks, and it looks like that's handled properly. I think it'll be hard to track down what happened unless we can look at the lock state using a vmcore or so. I wonder if it'd be possible to re-trigger the deadlock, and then panic the system to collect a core dump? --=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-282169-3630-ObgPitkSmF>