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
| ||
|
Date: Wed, 08 Nov 2006 18:45:30 +0900 From: Fernando Luis Vázquez Cao <fernando@....ntt.co.jp> To: Jes Sorensen <jes@....com> Cc: Andrew Morton <akpm@...l.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, bjorn_helgaas@...com, Nick Piggin <nickpiggin@...oo.com.au>, Robin Holt <holt@....com>, Dean Nelson <dcn@....com>, Hugh Dickins <hugh@...itas.com>, Linus Torvalds <torvalds@...l.org>, linux-ia64 <linux-ia64@...r.kernel.org>, Tony Luck <tony.luck@...il.com> Subject: Re: [PATCH 0/1] mspec driver: compile error On Wed, 2006-11-08 at 10:42 +0100, Jes Sorensen wrote: > Fernando Luis Vázquez Cao wrote: > > On Tue, 2006-11-07 at 13:35 -0800, Andrew Morton wrote: > > The problem occurs because i386 (as expected) does not define > > IA64_UNCACHED_ALLOCATOR. I thought that making the select expression > > depend on IA64 as shown below might silence allmodconfig: > > > > select IA64_UNCACHED_ALLOCATOR if IA64 > > > > But my guess was wrong and the same warning appeared. It seems that "if" > > expressions do not prevent allmodconfig from checking the symbol > > indicated by the select the "if" is conditioning. By the way, is this > > the expected behaviour? If so, we need to get rid of the reverse > > dependency, modify the "depends on" line accordingly, and make > > IA64_UNCACHED_ALLOCATOR selectable. I may be missing the whole point so > > please correct if I am wrong. > > This patch is a bad solution as it requires people to manually select > the uncached allocator. It should be enabled automatically by MSPEC, > not the other way round. > > Given that MSPEC is clearly marked as depending on IA64, it seems bogus > for i386 allmodconfig to barf over it and the problem should be fixed > there instead IMHO. Agreed. That is why I asked if that was allmodconfig's expected behaviour. Andrew? Cheers, Fernando - 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/
Powered by blists - more mailing lists