Date: Sat, 21 Jan 2017 21:02:10 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 210315] panic: destroying non-empty racct: 2113536 allocated for resource 4 Message-ID: <bug-210315-8-v2tmuFLgdg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-210315-8@https.bugs.freebsd.org/bugzilla/> References: <bug-210315-8@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=3D210315 --- Comment #6 from Andriy Gapon <avg@FreeBSD.org> --- Disabling the checks would, of course, make the symptoms disappear. But I still wonder what causes the problem(s). In Larry's case it's especially strange, because starting with racct_set_locked() all calculations are done under the lock. So, how can i= t be possible that we end up with any value other than zero in racct_adjust_resource()? Essentially we do: delta =3D 0 - value; value =3D value + delta; It would be interesting to examine the coredump with kgdb. maybe it would give some clues about how the impossible became possible. FWIW, I was not able to find any write access to r_resources that was not protected by racct_lock. --=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-210315-8-v2tmuFLgdg>