linux-kernel - Re: 'struct task_struct' has no member named 'mems

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: <Pine.LNX.4.64.0701121324060.2969@schroedinger.engr.sgi.com>
Date:	Fri, 12 Jan 2007 13:28:01 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	Paul Jackson <pj@....com>
cc:	akpm@...l.org, sander@...ilis.net, linux-kernel@...r.kernel.org
Subject: Re: 'struct task_struct' has no member named 'mems_allowed'  (was:
 Re: 2.6.20-rc4-mm1)

On Fri, 12 Jan 2007, Paul Jackson wrote:

> Argh - minor detail, but this is the first (outside of fs/proc/base.c)
> "#ifdef CONFIG_CPUSETS" in a kernel *.c file.  I prefer to avoid that.

Sorry but there will be number of those once we get the dirty writeback 
for cpusets fixed. Did you review that patchset (only internally mailed 
so far).

I do not think it makes much sense to do these macros for the single 
occurrence here and otherwise. Having the #ifdef here is much clearer.
Also the #ifdef is in already NUMA specific code.
-
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/