Date: Wed, 01 Feb 2023 15:38:08 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 269277] On 12.3, process-shared mutex may fail locking operations after usage of ANOTHER process-shared mutex. Message-ID: <bug-269277-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D269277 Bug ID: 269277 Summary: On 12.3, process-shared mutex may fail locking operations after usage of ANOTHER process-shared mutex. Product: Base System Version: 12.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: rau8344@gmail.com Created attachment 239841 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D239841&action= =3Dedit Minimal code to recreate issue On FreeBSD 12.3 amd64, a process-shared mutex may fail locking operations a= fter usage of ANOTHER process-shared mutex. Original issue was seen running a particular sequence of unit tests against a complex codebase; sometimes saw= two threads lock the same mutex at the same time, or fail on lock with EINVAL. Issue recreated=20 Recreated the EINVAL issue with a minimal example on a single thread (see attached), both with gtest and without. Tested on two physical quad-core machines (a Beckhoff 2040 and a Beckhoff 2042). --=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-269277-227>