linux-kernel - Re: Voyager phys_cpu_present

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: <20080421195148.GG8770@elte.hu>
Date:	Mon, 21 Apr 2008 21:51:48 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
Cc:	Adrian Bunk <bunk@...nel.org>,
	Alexey Starikovskiy <astarikovskiy@...e.de>,
	tglx@...utronix.de, hpa@...or.com, linux-kernel@...r.kernel.org
Subject: Re: Voyager phys_cpu_present_map compile error


* James Bottomley <James.Bottomley@...senPartnership.com> wrote:

> > thanks, the three patches below should fix it.
> > 
> > i ended up excluding Voyager configs from our test space some time 
> > ago (and VISWS as well - there's one more visws fix in x86.git), 
> > that's how this broke. These subarchitectures seem not to be used at 
> > all and the code wont boot on normal PCs. We could mark it BROKEN 
> > but the fix seems simple in any case.
> 
> The voyager pieces of this code look fine to me.  I can't test at the 
> moment because we're having the carpets cleaned and I can't get down 
> into the cellar where the systems are, but I'll do so shortly.

ok, that's good enough - that's why i excluded it from the auto-qa 
test-space as well. Adrian, could you please remove it from your config 
testset as well? If a user enables that config option it wont boot 
anyway so it's not a problem in practice.

	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/