linux-kernel - Re: Fwd: Commit 76a2a6ee8a0660a29127f05989ac59ae1ce865fa breaks PXA270 (at least)?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 31 Jul 2008 23:37:41 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Russell King - ARM Linux <linux@....linux.org.uk>,
	a.p.zijlstra@...llo.nl, vatsa@...ux.vnet.ibm.com, efault@....de,
	linux-kernel@...r.kernel.org
Subject: Re: Fwd: Commit 76a2a6ee8a0660a29127f05989ac59ae1ce865fa breaks
	PXA270 (at least)?


* Andrew Morton <akpm@...ux-foundation.org> wrote:

> On Tue, 29 Jul 2008 23:31:05 +0100
> Russell King - ARM Linux <linux@....linux.org.uk> wrote:
> 
> > But then some bright spark thought it would be a good idea to get
> > rid of printk_clock().
> 
> <does git-log, searches for printk_clock>

i think this is a fresh regression via the introduction of 
kernel/sched_clock.c. We lost the (known) early-init behavior of 
cpu_clock() in the !UNSTABLE_SCHED_CLOCK case. The fix would be to 
restore that, not to reintroduce printk_clock().

Peter, any ideas?

	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/