linux-kernel - Re: linux-next ia64 build problems in slqb

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:	Tue, 21 Apr 2009 10:35:57 -0400 (EDT)
From:	Christoph Lameter <cl@...ux.com>
To:	Pekka Enberg <penberg@...helsinki.fi>
cc:	"Luck, Tony" <tony.luck@...el.com>, Nick Piggin <npiggin@...e.de>,
	linux-kernel@...r.kernel.org, randy.dunlap_ocs10g@...cle.com,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next ia64 build problems in slqb

On Tue, 21 Apr 2009, Pekka Enberg wrote:

> On Tue, Apr 21, 2009 at 1:08 AM, Luck, Tony <tony.luck@...el.com> wrote:
> > The ia64 "allnoconfig" build ends up with the (possibly dubious) combination
> > of .config options:
> >
> >        CONFIG_SMP=n
> >        CONFIG_NUMA=y
>
> Yeah, I don't think the combination makes much sense and x86 doesn't
> allow it. Can we fix that in ia64 Kconfig? That said, this seems to
> come up with every architecture except x86, so if someone is kind
> enough to send me a tested fix for slqb, I'll just go ahead and apply
> it.

Tony runs tests with this configuration. This is an established
configuration and has been historically supported.