All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	JoonSoo Kim <js1304@gmail.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Vegard Nossum <vegard.nossum@gmail.com>,
	Christoph Lameter <cl@linux.com>, Rus <rus@sfinxsoft.com>,
	Ben Hutchings <ben@decadent.org.uk>,
	stable@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch v2] mm, slub: ensure irqs are enabled for kmemcheck
Date: Tue, 10 Jul 2012 22:44:03 +0300 (EEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1207102243540.1899@tux.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.1207091400090.23926@chino.kir.corp.google.com>

On Mon, 9 Jul 2012, David Rientjes wrote:
> kmemcheck_alloc_shadow() requires irqs to be enabled, so wait to disable
> them until after its called for __GFP_WAIT allocations.
> 
> This fixes a warning for such allocations:
> 
> 	WARNING: at kernel/lockdep.c:2739 lockdep_trace_alloc+0x14e/0x1c0()
> 
> Acked-by: Fengguang Wu <fengguang.wu@intel.com>
> Acked-by: Steven Rostedt <rostedt@goodmis.org>
> Tested-by: Fengguang Wu <fengguang.wu@intel.com>
> Signed-off-by: David Rientjes <rientjes@google.com>

Applied, thanks!

WARNING: multiple messages have this Message-ID (diff)
From: Pekka Enberg <penberg@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	JoonSoo Kim <js1304@gmail.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Vegard Nossum <vegard.nossum@gmail.com>,
	Christoph Lameter <cl@linux.com>, Rus <rus@sfinxsoft.com>,
	Ben Hutchings <ben@decadent.org.uk>,
	stable@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch v2] mm, slub: ensure irqs are enabled for kmemcheck
Date: Tue, 10 Jul 2012 22:44:03 +0300 (EEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1207102243540.1899@tux.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.1207091400090.23926@chino.kir.corp.google.com>

On Mon, 9 Jul 2012, David Rientjes wrote:
> kmemcheck_alloc_shadow() requires irqs to be enabled, so wait to disable
> them until after its called for __GFP_WAIT allocations.
> 
> This fixes a warning for such allocations:
> 
> 	WARNING: at kernel/lockdep.c:2739 lockdep_trace_alloc+0x14e/0x1c0()
> 
> Acked-by: Fengguang Wu <fengguang.wu@intel.com>
> Acked-by: Steven Rostedt <rostedt@goodmis.org>
> Tested-by: Fengguang Wu <fengguang.wu@intel.com>
> Signed-off-by: David Rientjes <rientjes@google.com>

Applied, thanks!

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2012-07-10 19:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-08  4:00 WARNING: __GFP_FS allocations with IRQs disabled (kmemcheck_alloc_shadow) Fengguang Wu
2012-07-08 16:12 ` JoonSoo Kim
2012-07-08 16:12   ` JoonSoo Kim
2012-07-08 23:01   ` David Rientjes
2012-07-08 23:01     ` David Rientjes
2012-07-09  1:52     ` Fengguang Wu
2012-07-09  1:52       ` Fengguang Wu
2012-07-09  9:09     ` Pekka Enberg
2012-07-09  9:09       ` Pekka Enberg
2012-07-09 10:36       ` [patch] mm, slub: ensure irqs are enabled for kmemcheck David Rientjes
2012-07-09 10:36         ` David Rientjes
2012-07-09 13:46         ` Steven Rostedt
2012-07-09 13:46           ` Steven Rostedt
2012-07-09 14:06           ` Fengguang Wu
2012-07-09 14:06             ` Fengguang Wu
2012-07-09 21:00           ` [patch v2] " David Rientjes
2012-07-09 21:00             ` David Rientjes
2012-07-10 19:44             ` Pekka Enberg [this message]
2012-07-10 19:44               ` Pekka Enberg
2012-07-09 13:52     ` WARNING: __GFP_FS allocations with IRQs disabled (kmemcheck_alloc_shadow) JoonSoo Kim
2012-07-09 13:52       ` JoonSoo Kim
2012-07-09 13:55   ` Christoph Lameter
2012-07-09 13:55     ` Christoph Lameter
2012-07-09 13:52 ` Christoph Lameter

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=alpine.LFD.2.02.1207102243540.1899@tux.localdomain \
    --to=penberg@kernel.org \
    --cc=ben@decadent.org.uk \
    --cc=cl@linux.com \
    --cc=fengguang.wu@intel.com \
    --cc=js1304@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --cc=rostedt@goodmis.org \
    --cc=rus@sfinxsoft.com \
    --cc=stable@vger.kernel.org \
    --cc=vegard.nossum@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.