linux-kernel - Re: [tip:tracing/urgent] tracing: Fix event format export

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] [day] [month] [year] [list]

Message-ID: <20091206171107.GA22298@elte.hu>
Date:	Sun, 6 Dec 2009 18:11:07 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Steven Rostedt <rostedt@...dmis.org>, mingo@...hat.com,
	hpa@...or.com, linux-kernel@...r.kernel.org, tglx@...utronix.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:tracing/urgent] tracing: Fix event format export

* Johannes Berg <johannes@...solutions.net> wrote:

> On Thu, 2009-12-03 at 15:55 +0100, Ingo Molnar wrote:
> 
> > > Any reason that this did not make it into Mainline? 2.6.32 is out, and 
> > > Johannes Berg was depending on this for his users.
> > 
> > Yeah, it narrowly missed the last -rc (-rc8), and we only push 
> > post-final-rc fixes for serious show-stopper regressions.
> 
> You have an interesting definition of "narrowly missed":
> 
> $ git show v2.6.32-rc8
> ...
> Date:   Thu Nov 19 14:32:50 2009 -0800
> ...
> $ git show --pretty=fuller 811cb50baf63461ce0bdb234927046131fc7fa8b
> ...
> CommitDate: Fri Nov 13 22:20:34 2009 -0500

Yes, it came in late, after -rc7 and just two weeks before the final 
2.6.32 kernel was released. Please test linux-next or -tip more 
frequently if you want fixes to go upstream sooner.

> And Steven's pull request for this very simple fix was from the 14th. 
> That's 5 days until -rc8.

We are extra careful in late -rc's - and per Linus's request we are only 
pushing fixes for serious regressions, and even those we only push after 
careful testing. That's a few days commit life-time at minimum in the 
usual case.

> So maybe I have a personality problem, but suck it up -- you're wrong 
> this time.

No need to complain - the fix is upstream now and will be in 2.6.32.1 - 
within 1-2 weeks. If that's not fast enough for you then you can 
cherry-pick upstream commit 811cb50baf63461ce0bdb234927046131fc7fa8b 
into your tree right now.

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/