From: Dave Jones <davej@codemonkey.org.uk>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Tejun Heo <tj@kernel.org>
Subject: pids_free double free.
Date: Thu, 19 Nov 2015 23:18:36 -0500 [thread overview]
Message-ID: <20151120041836.GA18390@codemonkey.org.uk> (raw)
One of my debian boxes got a systemd update. After rebooting,
I started seeing a use-after-free trace, followed by a lockup.
I have two slightly different traces from separate boots,
which may give some clue as to how it's getting free'd in two ways..
http://codemonkey.org.uk/junk/IMG_0474.jpg
http://codemonkey.org.uk/junk/IMG_0476.jpg
This isn't new, I booted back to 4.3, and hit slab debugging warnings
from the same code. (At the least it was broken differently)
The WARN_ON referenced in the 2nd trace is this..
static void pids_cancel(struct pids_cgroup *pids, int num)
{
/*
* A negative count (or overflow for that matter) is invalid,
* and indicates a bug in the `pids` controller proper.
*/
WARN_ON_ONCE(atomic64_add_negative(-num, &pids->counter));
}
Dave
next reply other threads:[~2015-11-20 4:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 4:18 Dave Jones [this message]
[not found] ` <20151120041836.GA18390-rdkfGonbjUTCLXcRTR1eJlpr/1R2p/CL@public.gmane.org>
2015-11-20 20:48 ` pids_free double free Tejun Heo
2015-11-20 20:48 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151120041836.GA18390@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.