From: Rusty Russell <rusty@rustcorp.com.au>
To: Johannes Weiner <hannes@saeurebad.de>
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>
Subject: Re: Dangerous code in cpumask_of_cpu?
Date: Tue, 8 Jul 2008 19:33:42 +1000 [thread overview]
Message-ID: <200807081933.42594.rusty@rustcorp.com.au> (raw)
In-Reply-To: <87iqvgn4c1.fsf@saeurebad.de>
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.
next prev parent reply other threads:[~2008-07-08 9:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 8:16 Dangerous code in cpumask_of_cpu? Rusty Russell
2008-07-08 8:35 ` Johannes Weiner
2008-07-08 8:54 ` Johannes Weiner
2008-07-08 9:03 ` Johannes Weiner
2008-07-08 9:28 ` Johannes Weiner
2008-07-08 15:29 ` Mike Travis
2008-07-09 2:22 ` Rusty Russell
2008-07-09 14:42 ` Mike Travis
2008-07-08 9:33 ` Rusty Russell [this message]
2008-07-08 10:24 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200807081933.42594.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=clameter@sgi.com \
--cc=hannes@saeurebad.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=travis@sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.