From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: perf: out-of-bounds write in perf_callchain_store
Date: Tue, 6 Sep 2016 11:44:34 -0300 [thread overview]
Message-ID: <20160906144434.GB11557@kernel.org> (raw)
In-Reply-To: <20160906143608.GF3318@worktop.controleur.wifipass.org>
Em Tue, Sep 06, 2016 at 04:36:08PM +0200, Peter Zijlstra escreveu:
> On Tue, Sep 06, 2016 at 03:42:40PM +0200, Dmitry Vyukov wrote:
> > Hello,
> >
> > The following program trigger an out-of-bounds write in
> > perf_callchain_store (if run in a parallel loop):
> >
> > https://gist.githubusercontent.com/dvyukov/c05d883e776a353a1d063b670f50bde6/raw/1c8906b1aacfbd8a0cc0b5cf0cc4d0535345e497/gistfile1.txt
> >
> >
> > BUG: KASAN: slab-out-of-bounds in perf_callchain_user+0xe65/0xfc0 at
> > addr ffff88003e162840
> > Write of size 8 by task syz-executor/22516
> > CPU: 0 PID: 22516 Comm: syz-executor Not tainted 4.8.0-rc5-next-20160905+ #14
> > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
> > ffffffff886b6fe0 ffff88003ec07738 ffffffff82db81a9 ffffffff00000000
> > fffffbfff10d6dfc ffff88003e800a00 ffff88003e161740 ffff88003e163740
> > 0000000000000001 ffff88003e162840 ffff88003ec07760 ffffffff8180b2ec
> > Call Trace:
> > [<ffffffff8180b9c7>] __asan_report_store8_noabort+0x17/0x20
> > mm/kasan/report.c:332
> > [< inline >] perf_callchain_store include/linux/perf_event.h:1146
> > [<ffffffff81014925>] perf_callchain_user+0xe65/0xfc0 arch/x86/events/core.c:2441
> > [<ffffffff816c5f48>] get_perf_callchain+0x448/0x680 kernel/events/callchain.c:235
> > [<ffffffff816c62cd>] perf_callchain+0x14d/0x1a0 kernel/events/callchain.c:191
>
> Urgh, that callchain code is a pain with that context/entries
> separation. But I can't see an obvious overrun there.
>
> But WTF is max_contexts a sysctl? that doesn't seen to make any kind of
> sense.
>
> Acme, can you untangle that stuff and spot the fail?
I looked at it briefly some moments ago, couldn't find it so far, have
to look at what was behind adding a sysctl for that :-\
And yeah, that entry/ctx thing, IIRC, was done to reduce patch size,
probably needs some polishing to become clearer.
- Arnaldo
next prev parent reply other threads:[~2016-09-06 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 13:42 Dmitry Vyukov
2016-09-06 14:36 ` Peter Zijlstra
2016-09-06 14:44 ` Arnaldo Carvalho de Melo [this message]
2016-09-06 14:49 ` Dmitry Vyukov
2016-09-06 15:05 ` Arnaldo Carvalho de Melo
2016-09-06 15:18 ` Dmitry Vyukov
2016-09-06 15:06 ` Peter Zijlstra
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=20160906144434.GB11557@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome