Date: Fri, 18 Mar 2022 18:45:49 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262633] Missing mtx protecting variable prison->pr_prison_racct Message-ID: <bug-262633-227-0C51fYrxo4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262633-227@https.bugs.freebsd.org/bugzilla/> References: <bug-262633-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=3D262633 firk@cantconnect.ru changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #232558|text/x-csrc |text/plain mime type| | --- Comment #3 from firk@cantconnect.ru --- Created attachment 232558 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D232558&action= =3Dedit test program Added a test program. How to use: ./bug-262633-test 100000 3 Second value: 0 =3D fake run; 1 =3D only spam racct increment/decrement; 2 =3D only spam jail renaming (may be used to verify time consumed in LIST_FOREACH()); 3 =3D do both - will lead to panic First value: number of prison_racct structs to populate (note that they don't get depopulated until system reboot) I made a panic with this value =3D 10000 once; value =3D 30000 leads to = a panic very fast (but need to wait initializing of rctls). Panic reasons vary, but I think the source of all them is this bug. --=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-262633-227-0C51fYrxo4>