public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	syzkaller <syzkaller@googlegroups.com>
Subject: Re: perf: use-after-free in perf_event_for_each
Date: Tue, 24 Jan 2017 14:17:48 +0100	[thread overview]
Message-ID: <20170124131748.GD6536@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20170123170442.GL6515@twins.programming.kicks-ass.net>

On Mon, Jan 23, 2017 at 06:04:42PM +0100, Peter Zijlstra wrote:
> On Mon, Jan 23, 2017 at 02:30:12PM +0100, Dmitry Vyukov wrote:
> > Hello,
> > 
> > The following program triggers use-after-free in perf_event_for_each:
> > https://gist.githubusercontent.com/dvyukov/f1c354a8356e42f4d0b3d912e1bec956/raw/31d7ecdf6dc2c7327b80ef8581a39c823bbe405d/gistfile1.txt

I've been running 60 concurrent instances of that thing for hours now,
and have not been able to reproduce :-/

I did enable CONFIG_KASAN but otherwise booted as normal, and the thing
says:

[    0.000000] kasan: KernelAddressSanitizer initialized

Is there anything else I should do?

I've ran out of ideas and it would be very helpful if I could prod at
something that fails...

  reply	other threads:[~2017-01-24 13:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 13:30 perf: use-after-free in perf_event_for_each Dmitry Vyukov
2017-01-23 17:04 ` Peter Zijlstra
2017-01-24 13:17   ` Peter Zijlstra [this message]
2017-01-24 13:29     ` Dmitry Vyukov
2017-01-24 13:49       ` Peter Zijlstra
2017-01-26 15:39 ` Peter Zijlstra
2017-01-27  9:08   ` Dmitry Vyukov
2017-01-27 13:02   ` Alexander Shishkin
2017-01-30 11:52   ` [tip:perf/core] perf/core: Fix use-after-free bug tip-bot for 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=20170124131748.GD6536@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=syzkaller@googlegroups.com \
    /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