From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Mike Travis" <travis@sgi.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
mm-commits@vger.kernel.org, "Yinghai Lu" <yhlu.kernel@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] x86: Add check for node passed to node_to_cpumask V3
Date: Thu, 3 Jul 2008 10:55:34 +0200 [thread overview]
Message-ID: <19f34abd0807030155x22b0033dj780830bad840216f@mail.gmail.com> (raw)
In-Reply-To: <20080703084401.GB7873@elte.hu>
On Thu, Jul 3, 2008 at 10:44 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Mike Travis <travis@sgi.com> wrote:
>
>> Subject: [PATCH 1/1] x86: Add check for node passed to node_to_cpumask V3
>>
>> * When CONFIG_DEBUG_PER_CPU_MAPS is set, the node passed to
>> node_to_cpumask and node_to_cpumask_ptr should be validated.
>> If invalid, then a dump_stack is performed and a zero cpumask
>> is returned.
>>
>> Based on "Fri Jun 27 10:06:06 PDT 2008" tip/master... ;-)
>>
>> Signed-off-by: Mike Travis <travis@sgi.com>
>> ---
>> V2: Slightly different version to remove a compiler warning.
>> V3: Redone to reflect moving setup.c -> setup_percpu.c
>
> applied to tip/x86/unify-setup - thanks Mike.
>
> Vegard, can i add your Acked-by too?
To be honest, I'd prefer that the function returns a const pointer.
Mike and I have both reviewed all callers independently and concluded
that there is no problem in doing this, and that, in fact, this is the
correct way to deal with it.
So if Mike submits a V4 with this const return type, or another patch
on top of this one, I'll ack it :-)
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-07-03 12:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806090918.m599Ib0G012837@imap1.linux-foundation.org>
[not found] ` <19f34abd0806090420r4100241cgb4b828441de3b102@mail.gmail.com>
[not found] ` <20080609113547.GA1534@elte.hu>
[not found] ` <484D54F2.4070603@sgi.com>
[not found] ` <20080626113229.GB29619@elte.hu>
2008-06-26 16:26 ` [PATCH 1/1] x86: Add check for node passed to node_to_cpumask Mike Travis
2008-06-27 2:39 ` [PATCH 1/1] x86: Add check for node passed to node_to_cpumask V2 Mike Travis
2008-06-27 17:10 ` [PATCH 1/1] x86: Add check for node passed to node_to_cpumask V3 Mike Travis
2008-06-27 17:24 ` Vegard Nossum
2008-06-27 18:03 ` Mike Travis
2008-06-29 11:34 ` Vegard Nossum
2008-06-29 12:40 ` Mike Travis
2008-07-03 8:44 ` Ingo Molnar
2008-07-03 8:55 ` Vegard Nossum [this message]
2008-07-03 9:01 ` Ingo Molnar
2008-07-08 17:06 ` [PATCH 1/1] x86: Change _node_to_cpumask_ptr to return const ptr Mike Travis
2008-07-08 17:35 ` Vegard Nossum
2008-07-08 18:05 ` Mike Travis
2008-07-08 18:22 ` Vegard Nossum
2008-07-08 20:51 ` Mike Travis
2008-07-08 21:21 ` Vegard Nossum
2008-07-08 21:28 ` Mike Travis
2008-07-08 21:35 ` Mike Travis
2008-07-08 21:52 ` Vegard Nossum
2008-07-13 17:12 ` Ingo Molnar
2008-07-07 17:23 ` [PATCH 1/1] x86: Add check for node passed to node_to_cpumask V3 Mike Travis
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=19f34abd0807030155x22b0033dj780830bad840216f@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=travis@sgi.com \
--cc=yhlu.kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®