Date: Sat, 12 Nov 2022 12:42:50 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262587] panic: lock (sleep mutex) umtxql not locked @ /usr/src/sys/sys/umtxvar.h:262 on 14-current master-n253798-8cdecdecb43 Message-ID: <bug-262587-227-72eTbfWxby@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262587-227@https.bugs.freebsd.org/bugzilla/> References: <bug-262587-227@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=3D262587 --- Comment #21 from commit-hook@FreeBSD.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3D62e1bb424584ca6a46e6224801d25b9fc= 6ca5ef9 commit 62e1bb424584ca6a46e6224801d25b9fc6ca5ef9 Author: Alexander Motin <mav@FreeBSD.org> AuthorDate: 2022-03-21 23:43:39 +0000 Commit: Hans Petter Selasky <hselasky@FreeBSD.org> CommitDate: 2022-11-12 11:59:27 +0000 Fix umtxq_sleep() regression caused by 56070dd2e4d. umtxq_requeue() moves the queue to a different hash chain and different lock, so we can't rely on msleep_sbt() reacquiring the same old lock. We have to use PDROP and update the queue chain and so lock pointer. PR: 262587 (cherry picked from commit fd6ca665d206b74970e7c01d06ae06fed71500fc) sys/kern/kern_umtx.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) --=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-262587-227-72eTbfWxby>