From: Mike Travis <travis@sgi.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@redhat.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] cpumask: add alloc_cpumask_var_node
Date: Mon, 15 Dec 2008 19:47:51 -0800 [thread overview]
Message-ID: <494724E7.4090701@sgi.com> (raw)
In-Reply-To: <20081216143045.2afa85a7.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi Mike,
>
> Just some simple comments.
>
> On Mon, 15 Dec 2008 18:32:51 -0800 Mike Travis <travis@sgi.com> wrote:
>> +/**
>> + * alloc_cpumask_var - return an allocated struct cpumask
>> + * @mask: pointer to cpumask_var_t where the cpumask is returned
>> + * @cpu: GFP_ flags
> ^^^
> flags
Hmm, even the simplest changes can go awry... ;-)
>
>> + * alloc_cpumask_var_node - return an allocated struct cpumask on a
>> + * specific node.
>> + * @mask: pointer to cpumask_var_t where the cpumask is returned
>> + * @cpu: GFP_ flags
> ^^^
> flags
Gotcha.
>
>> + * @node: node to allocate memory on
>> + *
>> + * Only defined when CONFIG_CPUMASK_OFFSTACK=y, otherwise is
>> + * a nop returning a constant 1 (in <linux/cpumask.h>)
>> + * Returns TRUE if memory allocation succeeded, FALSE otherwise.
>> + */
>> +bool alloc_cpumask_var_node(cpumask_var_t *mask, gfp_t flags, int node)
>> +{
>> + if (likely(slab_is_available()))
>> + *mask = kmalloc_node(cpumask_size(), flags, node);
>> + else {
>> +#ifdef CONFIG_DEBUG_PER_CPU_MAPS
>> + printk(KERN_ERR
>> + "=> alloc_cpumask_var_node: kmalloc not available!\n");
>> + dump_stack();
>> +#endif
>> + *mask = NULL;
>> + }
>> +#ifdef CONFIG_DEBUG_PER_CPU_MAPS
>> + if (!*mask) {
>> + printk(KERN_ERR "=> alloc_cpumask_var_node: failed!\n");
>> + dump_stack();
>> + }
>> +#endif
>
> So if !slab_is_available() and CONFIG_DEBUG_PER_CPU_MAPS is set, we get
> two stack dumps?
Umm, you're right, one message should suffice... ;-)
Here's one place I discovered it in testing:
[ 0.000000] Initializing CPU#0
[ 0.000000] RCU-based detection of stalled CPUs is enabled.
[ 0.000000] => alloc_cpumask_var: kmalloc not available!
[ 0.000000] Pid: 0, comm: swapper Not tainted 2.6.28-rc8-128-defconfig.12151554-00944-g968ea6d
-dirty #21
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff8123b5bb>] alloc_cpumask_var+0x73/0xa7
[ 0.000000] [<ffffffff819197d0>] arch_early_irq_init+0x35/0xc3
[ 0.000000] [<ffffffff8192583d>] early_irq_init+0x57/0x59
[ 0.000000] [<ffffffff8190ab77>] start_kernel+0x1f9/0x3c2
[ 0.000000] [<ffffffff8190a29a>] x86_64_start_reservations+0xa9/0xad
[ 0.000000] [<ffffffff8190a39b>] x86_64_start_kernel+0xda/0xe1
[ 0.000000] => alloc_cpumask_var: failed!
<same as above>
...
The message clued me into the fact that the function was allocating
early and needed to be an alloc_bootmem_cpumask_var().
>
>> + * free_cpumask_var - frees memory allocated for a struct cpumask.
>> + * mask: cpumask to free
> ^
> missing '@'
>
>> + * free_bootmem_cpumask_var - frees bootmem memory allocated for a struct cpumask.
>> + * mask: cpumask to free
> ^
> here as well.
>
Will fix it up and resend.
Thanks!
Mike
next prev parent reply other threads:[~2008-12-16 3:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 2:32 [PATCH 1/1] cpumask: add alloc_cpumask_var_node Mike Travis
2008-12-16 3:30 ` Stephen Rothwell
2008-12-16 3:47 ` Mike Travis [this message]
2008-12-16 4:19 ` [PATCH 1/1] cpumask: add alloc_cpumask_var_node V2 Mike Travis
2008-12-17 11:48 ` Rusty Russell
2008-12-17 18:11 ` 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=494724E7.4090701@sgi.com \
--to=travis@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).