linux-kernel - [GIT PULL] percpu fixes for 2.6.34-rc3

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]

Message-ID: <4BB951FE.3090402@kernel.org>
Date:	Mon, 05 Apr 2010 11:59:10 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: [GIT PULL] percpu fixes for 2.6.34-rc3

Hello, Linus.

Please pull from the following percpu branch.

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

lockdep was hardcoding conditions to determine whether an address
belongs to percpu area.  With recent percpu allocator changes, the
logic no longer is correct triggering bogus warning messages.  The
above branch implements is_kernel/module_percpu_address() and makes
lockdep use them instead.

Has been tested in linux-next and pulls cleanly into
db217dece3003df0841bacf9556b5c06aa097dae.

Thanks.

Randy Dunlap (1):
      module: add stub for is_module_percpu_address

Tejun Heo (2):
      module: encapsulate percpu handling better and record percpu_size
      percpu, module: implement and use is_kernel/module_percpu_address()

 include/linux/module.h |   11 +++++-
 include/linux/percpu.h |    7 +++
 kernel/lockdep.c       |   21 ++-------
 kernel/module.c        |  104 +++++++++++++++++++++++++++++++++--------------
 mm/percpu.c            |   26 ++++++++++++
 5 files changed, 121 insertions(+), 48 deletions(-)

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