Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1166409 > unrolled thread

Re: [RFC NEXT] mm: Fix suspicious RCU usage at kernel/sched/core.c:7318

Started byMartin KaFai Lau <kafai@fb.com>
First post2015-06-16 23:10 +0200
Last post2015-06-16 23:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [RFC NEXT] mm: Fix suspicious RCU usage at  kernel/sched/core.c:7318 Martin KaFai Lau <kafai@fb.com> - 2015-06-16 23:10 +0200

#1166409 — Re: [RFC NEXT] mm: Fix suspicious RCU usage at kernel/sched/core.c:7318

FromMartin KaFai Lau <kafai@fb.com>
Date2015-06-16 23:10 +0200
SubjectRe: [RFC NEXT] mm: Fix suspicious RCU usage at kernel/sched/core.c:7318
Message-ID<pC6hl-5N6-21@gated-at.bofh.it>
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@fb.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web