linux-kernel - Re: [PATCH] time: Revert to calling clock_was_set

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: <20140328070750.GB30107@gmail.com>
Date:	Fri, 28 Mar 2014 08:07:50 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	John Stultz <john.stultz@...aro.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] time: Revert to calling clock_was_set_delayed() while in
 irq context


* John Stultz <john.stultz@...aro.org> wrote:

> Ingo,
> 
> After testing a patch queued for 3.15, I noticed there was a WARNON 
> message that I realized was triggered by one of my patches that came 
> in the 3.14 merge window. I'm not very happy to find this now, but 
> sadly here it is. The fix is luckily fairly simple and just falls 
> back to previous behavior.
> 
> For tip/timers/urgent.

No problem - I've applied your fix to timers/urgent and will get it to 
Linus later today, after a bit of testing.

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/