linux-kernel - Re: perf/ftrace lockup on 3.12-rc6 with trigger code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131025101943.GA3481@gmail.com>
Date:	Fri, 25 Oct 2013 12:19:43 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Vince Weaver <vincent.weaver@...ne.edu>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Dave Jones <davej@...hat.com>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: perf/ftrace lockup on 3.12-rc6 with trigger code


* Steven Rostedt <rostedt@...dmis.org> wrote:

> > Urgh, I had turned those on to try to debug something and forgot 
> > to disable.  I feel like I saw this problem before I had those 
> > enabled so I guess I have to start from scratch fuzzing to see 
> > if I can get a more generally reproducible trace.

Btw., even if various config options are enabled, we don't want the 
kernel to lock up. So it might not be _the_ bug you are looking, but 
it certainly looks like _a_ bug.

> Looks like something is incorrectly enabling function tracer 
> within perf. Peter told me that there's some ref count bug that 
> may use data after being freed on exit.
> 
> I tried the program that you attached in you previous email, and 
> was not able to hit the bug. Are you able to hit the bug with that 
> code each time?

A full .config and a SHA1 of the tested tree would definitely be 
nice!

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/