linux-kernel - [GIT PULL] percpu fixes for 3.4-rc6

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

Date:	Thu, 10 May 2012 14:21:58 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org,
	Christoph Lameter <cl@...ux-foundation.org>,
	"Pavel V. Panteleev" <pp_84@...l.ru>,
	Catalin Marinas <catalin.marinas@....com>
Subject: [GIT PULL] percpu fixes for 3.4-rc6

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
--
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/