linux-kernel - Re: [patch] generic-ipi: fix backtrace in smp_call_function

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 08 Jan 2010 10:18:36 +0530
From:	David John <davidjon@...ontk.org>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
CC:	Rusty Russell <rusty@...tcorp.com.au>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [patch] generic-ipi: fix backtrace in smp_call_function_any()

On 01/08/2010 05:16 AM, Suresh Siddha wrote:
> On my westmere box, I see this backtrace with 2.6.33-rc kernels:
> 
>> cpumask_of_node(3): node > nr_node_ids(1)
>> Pid: 1, comm: swapper Not tainted 2.6.33-rc3-00097-g2c1f189 #223
>> Call Trace:
>>  [<ffffffff81028bb3>] cpumask_of_node+0x23/0x58
>>  [<ffffffff81061f51>] smp_call_function_any+0x65/0xfa
>>  [<ffffffff810160d1>] ? do_drv_read+0x0/0x2f
>>  [<ffffffff81015fba>] get_cur_val+0xb0/0x102
>>  [<ffffffff81016080>] get_cur_freq_on_cpu+0x74/0xc5
>>  [<ffffffff810168a7>] acpi_cpufreq_cpu_init+0x417/0x515
>>  [<ffffffff81562ce9>] ? __down_write+0xb/0xd
>>  [<ffffffff8148055e>] cpufreq_add_dev+0x278/0x922
> 
> fix it by using the cpu_to_node() and using the node number instead
> of the cpu for cpumask_of_node().
> 
> Signed-off-by: Suresh Siddha <suresh.b.siddha@...el.com>

Hi Suresh,

I have already sent a patch for this:
http://www.gossamer-threads.com/lists/linux/kernel/1173978?do=post_view_threaded

Can you ACK that instead?

Regards,
David.

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