linux-kernel - Re: [scheduler] BUG: unable to handle kernel paging request at 000000000000d110

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 30 Jul 2014 16:44:29 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Fengguang Wu <fengguang.wu@...el.com>
cc:	Christoph Lameter <cl@...ux-foundation.org>,
	Tejun Heo <tj@...nel.org>, Jet Chen <jet.chen@...el.com>,
	Su Tao <tao.su@...el.com>, Yuanhan Liu <yuanhan.liu@...el.com>,
	LKP <lkp@...org>, linux-kernel@...r.kernel.org
Subject: Re: [scheduler] BUG: unable to handle kernel paging request at
 000000000000d110

On Wed, 30 Jul 2014, Fengguang Wu wrote:

> 
> Hi Christoph,
> 
> The parent commit is clean in this case.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu.git for-3.17-consistent-ops
> commit 9b0c63851edaf54e909475fe2a0946f57810e98a
> Author:     Christoph Lameter <cl@...ux.com>
> AuthorDate: Fri Jun 20 14:31:18 2014 -0500
> Commit:     Tejun Heo <tj@...nel.org>
> CommitDate: Fri Jul 18 19:21:39 2014 -0400
> 
>     scheduler: Replace __get_cpu_var with this_cpu_ptr
>     
>     Convert all uses of __get_cpu_var for address calculation to use
>     this_cpu_ptr instead.
>     
>     Cc: Peter Zijlstra <peterz@...radead.org>
>     Acked-by: Ingo Molnar <mingo@...nel.org>
>     Signed-off-by: Christoph Lameter <cl@...ux.com>
>     Signed-off-by: Tejun Heo <tj@...nel.org>

All the instances in kernel/sched/* should be of the form 
*this_cpu_ptr(&mask) due to the special handling of struct cpumask *, 
correct?
--
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/