linux-kernel - [PATCH 0/2] kernel/module.c locking changes

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

Message-Id: <201005312130.17038.rusty@rustcorp.com.au>
Date:	Mon, 31 May 2010 21:30:15 +0930
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Brandon Philips <brandon@...p.org>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jon Masters <jonathan@...masters.org>,
	Tejun Heo <htejun@...il.com>,
	Masami Hiramatsu <mhiramat@...hat.com>
Subject: [PATCH 0/2] kernel/module.c locking changes

In response to Linus' almost-rational dislike of the lock-drop-and-regrab
patch, I've dug out and updated the fine-grained locking patch for module.c.
Simple testing here seems to work, and it might have a good effect on boot
times too (its original target).

Pull request for those who find that easier:

The following changes since commit 67a3e12b05e055c0415c556a315a3d3eb637e29e:
  Linus Torvalds (1):
        Linux 2.6.35-rc1

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6.git modules

Rusty Russell (3):
      module: fix reference to mod->percpu after freeing module.
      module: make locking more fine-grained.
      module: fix bne2 "gave up waiting for init of module libcrc32c"

 kernel/module.c |  151 +++++++++++++++++++++++++++++++++++-------------------
 1 files changed, 98 insertions(+), 53 deletions(-)

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