From: Peter Zijlstra <peterz@infradead.org>
To: Niklas Cassel <niklas.cassel@axis.com>
Cc: tj@kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] sched: leaf_cfs_rq_list use after free
Date: Fri, 11 Mar 2016 18:28:08 +0100 [thread overview]
Message-ID: <20160311172808.GF6344@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <56E2FA0F.4000803@axis.com>
On Fri, Mar 11, 2016 at 06:02:07PM +0100, Niklas Cassel wrote:
> > Can you describe a reliable reproducer?
>
> Right now I just do a reboot loop, systemd creates cgroups during boot
> this dump took 84 reboots. Harder to reproduce with more trace_printks.
Bugger, I don't have a single system with systemd on, so that'll be hard
to reproduce.
>
> CONFIG_SCHED_AUTOGROUP looks interesting though, might try that next week.
>
> Appears that the call comes from idle_balance or rebalance_domains,
> since they are the only ones that call load_balance.
Weird, balancing should very much be inside the cgroup, so if balancing
moves anything, there must be tasks to begin with, which still should
not be the case if we've called offline.
FWIW:
echo 1 > /debug/tracing/options/stacktrace
will add a stack trace to each trace_printk().
next prev parent reply other threads:[~2016-03-11 17:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 10:41 [BUG] sched: leaf_cfs_rq_list use after free Niklas Cassel
2016-03-10 12:54 ` Peter Zijlstra
2016-03-11 17:02 ` Niklas Cassel
2016-03-11 17:28 ` Peter Zijlstra [this message]
2016-03-11 18:20 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2016-03-12 9:42 Kazuki Yamaguchi
2016-03-12 13:59 ` Peter Zijlstra
2016-03-14 11:20 ` Peter Zijlstra
2016-03-14 12:09 ` Peter Zijlstra
2016-03-16 14:24 ` Tejun Heo
2016-03-16 14:44 ` Tejun Heo
2016-03-16 15:22 ` Peter Zijlstra
2016-03-16 16:50 ` Tejun Heo
2016-03-16 17:04 ` Peter Zijlstra
2016-03-16 17:49 ` Tejun Heo
2016-03-17 8:29 ` Niklas Cassel
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=20160311172808.GF6344@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niklas.cassel@axis.com \
--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.