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]

Message-Id: <20081013.000017.171095053.davem@davemloft.net>
Date:	Mon, 13 Oct 2008 00:00:17 -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


Bug fixes:

1) The change adding notify_cpu_starting() broke the sparc32 build
   (fix from Robert Reif), and missed adding the hook to sparc64.

2) chmc driver module init can crash on sun4v systems, because reading
   the %ver register is illegal on those chips, but since we didn't
   mark the %ver register asm with __volatile__ gcc could move it
   before the platform type guard test

Please pull, thanks a lot!

The following changes since commit 4480f15b3306f43bbb0310d461142b4e897ca45b:
  Randy Dunlap (1):
        MAINTAINERS: remove colon from headings

are available in the git repository at:

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

David S. Miller (2):
      sparc64: Add missing notify_cpu_starting() call.
      chmc: Mark %ver register inline asm with __volatile__

Robert Reif (1):
      sparc32: fix build errors

 arch/sparc/kernel/sun4d_smp.c |    1 +
 arch/sparc/kernel/sun4m_smp.c |    1 +
 arch/sparc64/kernel/chmc.c    |    2 +-
 arch/sparc64/kernel/smp.c     |    4 ++++
 4 files changed, 7 insertions(+), 1 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/