linux-kernel - Re: [tip:tracing/syscalls] tracing/core: fix early free of cpumasks

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: <alpine.DEB.2.00.0904012203250.30963@gandalf.stny.rr.com>
Date:	Wed, 1 Apr 2009 22:42:46 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
	fweisbec@...il.com, tglx@...utronix.de,
	Johannes Berg <johannes@...solutions.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <gregkh@...e.de>, linux-tip-commits@...r.kernel.org,
	stable@...nel.org
Subject: Re: [tip:tracing/syscalls] tracing/core: fix early free of
 cpumasks


On Thu, 2 Apr 2009, Ingo Molnar wrote:

> 
> * Steven Rostedt <rostedt@...dmis.org> wrote:
> 
> > This never made it into 2.6.29, nor do I see it yet in mainline.
> > 
> > This can cause unpredictable results with ftrace. We are freeing a 
> > cpu mask that will be later used.
> 
> Yes ... but CONFIG_OFFSTACK is only possible as a debug option right 
> now. So it's far less serious of an issue, it needs 2-3 unlikely 
> features to be combined.

And unfortunately for Johannes, he must have had all those features 
configured :-/  He spent pretty much the entire day trying to figure out 
why ftrace was broken.

-- Steve

> 
> The fix looks simple enough, so once the tracing tree is upstream, 
> we can forward it to -stable.
> 
> 	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/