linux-kernel - Re: [PATCH] timekeeping fix mismerge

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]

Date:	Mon, 14 May 2007 21:17:23 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	john stultz <johnstul@...ibm.com>
Subject: Re: [PATCH] timekeeping fix mismerge

On Mon, 2007-05-14 at 11:58 -0700, Andrew Morton wrote:
> Urgh, that was probably me trying to manage the maelstrom from a million
> monkeys mucking in the same code for multiple months, sigh.
> 
> So what do "broke" and "fix" mean in this context?  What are the
> consequences of this bug, and of its fix?  Is the above appropriate for
> 2.6.21.x and if so why?

clocksource_resume() is not called except from
unregister_time_interpolator(), which is definitely the wrong place.

No 2.6.21.x material, as the move of the timekeeping code happened after
2.6.21.

	tglx


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