Date: Fri, 18 Mar 2022 11:20:46 +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-0Vxt8hWtyX@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 --- Comment #1 from firk@cantconnect.ru --- What can be done: 1) disable racct - obviously not the case 2) rollback commit https://svnweb.freebsd.org/base?view=3Drevision&revision=3D221362 - seems a= lso not the case 3) disable jail renaming when racct enabled - personally I don't see any problems with this (I'm not sure if jail renaming ever used by someone) 4) add protective lock for prison->pr_prison_racct It will works, but I don't think it is good idea. Currently, only protect= ed proc->p_ucred needed to get related jail racct pointer. Requiring any additional locks to do this will make racct code more complicated. 5) very complicated jail-rename procedure, locking all processes inside bef= ore renaming and unlocking them after; this will lead to some performance loss,= but since jail renaming never used, nobody will notice it; I'm not sure if this= is needed --=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-0Vxt8hWtyX>