linux-kernel - Re: ftrace 2.6.30-rc4: possible circular locking dependency

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.0905081124350.28378@gandalf.stny.rr.com>
Date:	Fri, 8 May 2009 11:25:23 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
	LKML <linux-kernel@...r.kernel.org>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: ftrace 2.6.30-rc4: possible circular locking dependency


On Fri, 8 May 2009, Ingo Molnar wrote:

> 
> * Steven Rostedt <rostedt@...dmis.org> wrote:
> 
> > 
> > Hi Tetsuo,
> > 
> > Thanks for the report. But we already have a fix for it. But the change is 
> > a bit of design change, and it is one of those things that is hard to know 
> > if we should push it up stream this late in the RCs.
> > 
> > We probably should. But the change affects two different subsystems. It 
> > affects ftrace as well as the module code. There's a bit of changes to the 
> > module code (Rusty being the maintainer) where we would be more 
> > comfortable if it goes via Rusty.
> > 
> > Rusty and Ingo,
> > 
> > What is the best way to get this change upstream?
> > 
> > Reference: http://lkml.org/lkml/2009/4/15/548
> > 
> > tip git SHA1: 93eb677d74a4f7d3edfb678c94f6c0544d9fbad2
> 
> Would be nice to have a non-conflicting version against latest -git 
> - which Tetsuo could test as well, and which i could apply if the 
> test is successful.

OK, I'll write up a patch.

-- Steve

--
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/