linux-kernel - [GIT]: Sparc

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:	Mon, 08 Sep 2008 13:59:01 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	torvalds@...ux-foundation.org
CC:	akpm@...ux-foundation.org, sparclinux@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: [GIT]: Sparc

Two SMP fixes for sparc64:

1) Conversion to generic SMP call function helpers didn't update the
   locking.  The sparc64 code was still using it's local "call lock"
   in it's cpu hotplug code, yet that isn't used for smp_call_function()
   et al. any longer.  Fix to use the locking interface exposed by
   the generic code.

2) Bug fix from Paul McKenney so that the online cpu map is cleared
   at the correct moment during cpu hotplug.  Otherwise an offline
   CPU can receive an interrupt and lots of code does not like that.

Please pull, thanks a lot.

The following changes since commit dbb8c35d9063fe233626865cc836fbc102fa083b:
  David S. Miller (1):
        sparc64: setup_valid_addr_bitmap_from_pavail() should be __init

are available in the git repository at:

  master.kernel.org:/pub/scm/linux/kernel/git/davem/sparc-2.6.git master

David S. Miller (1):
      sparc64: Fix IPI call locking.

Paul E. McKenney (1):
      sparc64: Prevent sparc64 from invoking irq handlers on offline CPUs

 arch/sparc64/kernel/smp.c |   14 ++++++--------
 1 files changed, 6 insertions(+), 8 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/