linux-kernel - Re: [ARM] Fix hard_smp_processor

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, 15 May 2007 18:49:37 +0900
From:	Simon Horman <horms@...ge.net.au>
To:	linux-kernel@...r.kernel.org,
	Fernando Luis Vazquez Cao <fernando@....ntt.co.jp>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [ARM] Fix hard_smp_processor_id compile error

On Tue, May 15, 2007 at 06:09:18PM +0900, Simon Horman wrote:
> On Tue, May 15, 2007 at 09:19:07AM +0100, Russell King wrote:
> > On Tue, May 15, 2007 at 11:18:50AM +0900, Simon Horman wrote:
> > > "Remove hardcoding of hard_smp_processor_id on UP systems",
> > > 2f4dfe206a2fc07099dfad77a8ea2f4b4ae2140f in Linus' tree, moved
> > > the definition of hard_smp_processor_id linux/smp.h to asm/smp.h
> > > for UP systems. This causes a regression on ARM as the definition
> > > was not added to asm-arm/smp.h.
> > > 
> > > Cc: Fernando Luis Vazquez Cao <fernando@....ntt.co.jp>
> > > Signed-off-by: Simon Horman <horms@...ge.net.au>
> > 
> > I took an alternative approach - since Integrator never had the complete
> > SMP support merged, I ripped it out of that platform.  Whether realview
> > suffers from the same thing or not I'm not sure - uniprocessor realview
> > is not something covered by the ARM default configuration files, and
> > therefore kautobuild won't check that configuration.
> 
> I can take a look into this. Is there a tree other than Linus'
> I should be working with?

Looking at Linus' it seems that for realview UP builds based on
realview_defconfig don't suffer hard_smp_processor_id breakage.
-
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/