public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Christoph Lameter <cl@linux-foundation.org>,
	"Pavel V. Panteleev" <pp_84@mail.ru>,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: [GIT PULL] percpu fixes for 3.4-rc6
Date: Thu, 10 May 2012 14:21:58 -0700	[thread overview]
Message-ID: <20120510212158.GH24636@google.com> (raw)

Hello, Linus.

This pull request contains two patches.  One is kmemleak annotation
fix which isn't critical.  The other is kinda serious.  Depending on
NUMA topology, percpu allocator may end up assigning overlapping
regions for the static percpu areas for different CPUs.  While
critical, the bug has been there for a very long time and only few
configurations seem to be affected (NUMA configurations w/ no memory
nodes for example) - so, while it's critical, it isn't exactly urgent.

If there isn't gonna be another rcX, I think it would be better to
pull the fix as part of the next merge window and backport through
-stable.

So, depending on release schedule, please consider pulling from the
following branch.

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu.git for-3.4-fixes

Catalin Marinas (1):
      kmemleak: Fix the kmemleak tracking of the percpu areas with !SMP

Tejun Heo (1):
      percpu: pcpu_embed_first_chunk() should free unused parts after all allocs are complete

 mm/percpu.c |   12 ++++++++++++
 1 files changed, 12 insertions(+), 0 deletions(-)

Thanks.

--
tejun

                 reply	other threads:[~2012-05-10 21:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20120510212158.GH24636@google.com \
    --to=tj@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pp_84@mail.ru \
    --cc=torvalds@linux-foundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox