From owner-freebsd-bugs@freebsd.org  Sat Jan 21 21:02:11 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F205CBA111
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sat, 21 Jan 2017 21:02:11 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4956C1DA7
 for <freebsd-bugs@FreeBSD.org>; Sat, 21 Jan 2017 21:02:11 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0LL2A4F015735
 for <freebsd-bugs@FreeBSD.org>; Sat, 21 Jan 2017 21:02:11 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 210315] panic: destroying non-empty racct: 2113536 allocated
 for resource 4
Date: Sat, 21 Jan 2017 21:02:10 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: avg@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jan 2017 21:02:11 -0000

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.=