mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vince Weaver <vincent.weaver@maine.edu>
To: Ingo Molnar <mingo@kernel.org>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
	Peter Zijlstra <peterz@infradead.org>,
	Huang Rui <ray.huang@amd.com>,
	linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: perf: fuzzer crashes immediately on AMD system
Date: Wed, 24 Aug 2016 09:20:24 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.20.1608240917580.2070@macbook-air> (raw)
In-Reply-To: <20160824091923.GB4340@gmail.com>

On Wed, 24 Aug 2016, Ingo Molnar wrote:
> If there's no progress finding the root cause I'd be happy to exchange a crash for 
> a leak ...

It's actually a crash of the program doing the perf_event_open() call, not 
a crash of the system (at least in my experience).

However, it's possible that if you have bad luck and if the kfree'd space 
is reused with just the right combination of values you could potentially 
end up crashing the system.

Vince

      reply	other threads:[~2016-08-24 13:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 14:32 Vince Weaver
2016-08-18 14:46 ` Vince Weaver
2016-08-19 10:01   ` Peter Zijlstra
2016-08-19 10:56     ` Peter Zijlstra
2016-08-19 15:03     ` Vince Weaver
2016-08-19 16:38       ` Vince Weaver
2016-08-20  4:44     ` Vince Weaver
2016-08-22 11:16     ` Huang Rui
2016-08-23  1:02       ` Vince Weaver
2016-08-23  2:54         ` Vince Weaver
2016-08-23  8:45           ` Peter Zijlstra
2016-08-23 11:53             ` Vince Weaver
2016-08-24  9:19               ` Ingo Molnar
2016-08-24 13:20                 ` Vince Weaver [this message]

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=alpine.DEB.2.20.1608240917580.2070@macbook-air \
    --to=vincent.weaver@maine.edu \
    --cc=acme@kernel.org \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=ray.huang@amd.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

all inboxes | Powered by JetHome®