From: Rusty Russell <rusty@rustcorp.com.au>
To: Johannes Weiner <hannes@saeurebad.de>
Subject: Re: Dangerous code in cpumask_of_cpu?
Date: Tue, 8 Jul 2008 19:33:42 +1000
User-Agent: KMail/1.9.9
Cc: Mike Travis <travis@sgi.com>, linux-kernel@vger.kernel.org,
       "H. Anvin" <hpa@zytor.com>, Christoph Lameter <clameter@sgi.com>,
       Ingo Molnar <mingo@elte.hu>
References: <200807081816.40623.rusty@rustcorp.com.au> <87myksn587.fsf@saeurebad.de> <87iqvgn4c1.fsf@saeurebad.de>
In-Reply-To: <87iqvgn4c1.fsf@saeurebad.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200807081933.42594.rusty@rustcorp.com.au>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 637
Lines: 17

On Tuesday 08 July 2008 18:54:38 Johannes Weiner wrote:
> Johannes Weiner <hannes@saeurebad.de> writes:
> > But then, this code should probably just evaluate to m without this
> > obscure *(&m) construct.
>
> This, however is still possible, no?

Unfortunately this change was specifically made in the changeset I refered to, 
so that the &cpumask_of_cpu() could be passed :(

Cheers,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/