linux-kernel - RE: [git pull] ia64 changes

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: <1FE6DD409037234FAB833C420AA843EC012F9F55@orsmsx424.amr.corp.intel.com>
Date:	Thu, 24 Apr 2008 17:25:06 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	"Adrian Bunk" <bunk@...nel.org>
Cc:	<torvalds@...ux-foundation.org>, <linux-kernel@...r.kernel.org>,
	<linux-ia64@...r.kernel.org>, "Mike Travis" <travis@....com>,
	"Russ Anderson" <rja@....com>
Subject: RE: [git pull] ia64 changes

>>       Build fix for CONFIG_NUMA=y && CONFIG_SMP=n
>>...
>
> Why is this an allowed configuration on ia64?

It shows up in allnoconfig ... probably because some
bit of Kconfig forces NUMA=y.

I can't imagine that it is ever a useful combination ... except to
find places in the code where people have:

#if defined(CONFIG_SMP)
 ...
#else

#if defined(CONFIG_NUMA) // !!! SMP=n, NUMA code???
  ...
#endif
#endif

Which is what happened, and is being fixed, here.

-Tony