linux-kernel - Re: [PATCH] sched: update_rq_clock() must skip ONE update

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: <20140401095548.GB1299@gmail.com>
Date:	Tue, 1 Apr 2014 11:55:48 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Mike Galbraith <umgwanakikbuti@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] sched: update_rq_clock() must skip ONE update


* Mike Galbraith <umgwanakikbuti@...il.com> wrote:

> On Mon, 2014-03-31 at 11:37 -0700, Linus Torvalds wrote: 
> > On Mon, Mar 31, 2014 at 11:27 AM, Mike Galbraith
> > <umgwanakikbuti@...il.com> wrote:
> > >
> > > Oh, I didn't cc you because I wanted it applied instantly as ultra
> > > critical, only because the chain of events might be of interest.
> > 
> > Ok. That was my main worry, since I was in the process or releasing
> > 3.14, and I just couldn't tell if the patch was something I should
> > worry about or not.
> > 
> > And it seems that not applying it was the right thing, which is all
> > that matters by now.
> 
> Yes.  Jocular red flag was to Peter and Ingo.  I don't try to bypass 
> them, that would be plain rude.  I've been known to help maintainers 
> a little, but I don't ever try to call the shots.  They do that 
> well.

Btw., in general feel free to Cc: Linus if a fix looks truly urgent, 
as neither Peter nor me might be around on a weekend, shortly before a 
release.

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/