linux-kernel - Re: linux-next: build failure after merge of the final tree (akpm tree related)

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]

Message-Id: <20111129211630.de8c0646.akpm@linux-foundation.org>
Date:	Tue, 29 Nov 2011 21:16:30 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	David Rientjes <rientjes@...gle.com>
Subject: Re: linux-next: build failure after merge of the final tree (akpm
 tree related)

On Wed, 30 Nov 2011 15:42:31 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi Andrew,
> 
> After merging the final tree, today's linux-next build (i386 defconfig)
> failed like this:
> 
> kernel/cpuset.c: In function 'cpuset_change_task_nodemask':
> kernel/cpuset.c:971:17: error: 'struct task_struct' has no member named 'mempolicy'
> 
> Caused by commit abf5d6d23d83 ("cpusets: stall when updating mems_allowed
> for mempolicy or disjoint nodemask") from the akpm tree.  The mempolicy
> member is only available when CONFIG_NUMA is set.
> 

This obviously can be hacked around, but one wonders whether we really
need to include things like cpuset_change_task_nodemask() in a
CONFIG_NUMA=n vmlinux?

--
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/