linux-kernel - Re: [PATCH] - Fix ordering of calls to uv_system_init & uv_cpu

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]

Date:	Tue, 23 Sep 2008 16:33:46 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jack Steiner <steiner@....com>
Cc:	tglx@...utronix.de, linux-kernel@...r.kernel.org,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [PATCH] - Fix ordering of calls to uv_system_init & uv_cpu_init


* Jack Steiner <steiner@....com> wrote:

> Fix problem caused by reordering of the calls to uv_cpu_init() &
> uv_system_init. Originally, uv_cpu_init() was called AFTER uv_system_init.
> This order was recently broken as a side-effect of other patches.
> 
> With this patch, initialization of cpu 0 is now done by the system_init
> call.
> 
> Signed-off-by: Jack Steiner <steiner@....com>

applied to tip/irq/sparseirq (where this bug originates from), thanks 
Jack!

	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/