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
| ||
|
Date: Tue, 16 Jun 2015 14:07:21 -0700 From: Martin KaFai Lau <kafai@...com> To: Larry Finger <Larry.Finger@...inger.net> CC: Tejun Heo <tj@...nel.org>, Catalin Marinas <catalin.marinas@....com>, Christoph Lameter <cl@...ux-foundation.org>, <linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>, Kernel Team <kernel-team@...com> Subject: Re: [RFC NEXT] mm: Fix suspicious RCU usage at kernel/sched/core.c:7318 On Mon, Jun 15, 2015 at 04:25:18PM -0500, Larry Finger wrote: > Additional backtrace lines are truncated. In addition, the above splat is > followed by several "BUG: sleeping function called from invalid context > at mm/slub.c:1268" outputs. As suggested by Martin KaFai Lau, these are the > clue to the fix. Routine kmemleak_alloc_percpu() always uses GFP_KERNEL > for its allocations, whereas it should use the value input to pcpu_alloc(). Just a minor nit, 'kmemleak_alloc_percpu() should follow the gfp from per_alloc()' may be a more accurate title to describe the patch. Acked-by: Martin KaFai Lau <kafai@...com> -- 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/
Powered by blists - more mailing lists