From: Ingo Molnar <mingo@elte.hu>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
"David S. Miller" <davem@davemloft.net>,
Al Viro <viro@zeniv.linux.org.uk>, Mike Travis <travis@sgi.com>
Subject: Re: [PATCH 1/3] cpumask: remove dangerous CPU_MASK_ALL_PTR, &CPU_MASK_ALL.
Date: Mon, 9 Feb 2009 11:16:42 +0100 [thread overview]
Message-ID: <20090209101642.GG20467@elte.hu> (raw)
In-Reply-To: <200902071809.17953.rusty@rustcorp.com.au>
* Rusty Russell <rusty@rustcorp.com.au> wrote:
> (Thanks to Al Viro for reminding me of this, via Ingo)
>
> CPU_MASK_ALL is the (deprecated) "all bits set" cpumask, defined as so:
>
> #define CPU_MASK_ALL (cpumask_t) { { ... } }
>
> Taking the address of such a temporary is questionable at best,
> unfortunately 321a8e9d (cpumask: add CPU_MASK_ALL_PTR macro) added
> CPU_MASK_ALL_PTR:
>
> #define CPU_MASK_ALL_PTR (&CPU_MASK_ALL)
>
> Which formalizes this practice. One day gcc could bite us over this
> usage (though we seem to have gotten away with it so far).
>
> So replace everywhere which used &CPU_MASK_ALL or CPU_MASK_ALL_PTR
> with the modern "cpu_all_mask" (a real struct cpumask *), and remove
> CPU_MASK_ALL_PTR altogether.
>
> Also remove the confusing and deprecated large-NR_CPUS-only
> "cpu_mask_all".
>
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
In general this should be expressed via this tag:
Reported-by: Al Viro <viro@zeniv.linux.org.uk>
Thanks,
Ingo
prev parent reply other threads:[~2009-02-09 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 7:39 [PATCH 1/3] cpumask: remove dangerous CPU_MASK_ALL_PTR, &CPU_MASK_ALL Rusty Russell
2009-02-09 10:16 ` Ingo Molnar [this message]
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=20090209101642.GG20467@elte.hu \
--to=mingo@elte.hu \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.org \
--cc=rusty@rustcorp.com.au \
--cc=travis@sgi.com \
--cc=viro@zeniv.linux.org.uk \
/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.