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: <20110512.004250.1962490475502866566.davem@davemloft.net>
Date:	Thu, 12 May 2011 00:42:50 -0400 (EDT)
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


Three sparc32 bug fixes here:

1) Correct unaligned pointer determination in sparc32 checksumming asm
   code, from Tkhai Kirill.

2) Sparc5 bootup busted because of incorrect CPU ID probing, fix from
   Sam Ravnborg.

3) Bad __init markings cause references to freed up memory after bootup,
   also from Sam Ravnborg.

Please pull, thanks a lot!

The following changes since commit 3568bd9720b4a775f28a718fcbb462ce2f386988:

  Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client (2011-05-11 19:13:34 -0700)

are available in the git repository at:

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

Sam Ravnborg (2):
      sparc32: fix section mismatch warnings in apc, pmc and time_32
      sparc32: fix sparcstation 5 boot

Tkhai Kirill (1):
      sparc32: Fixed unaligned memory copying in function __csum_partial_copy_sparc_generic

 arch/sparc/kernel/apc.c      |    2 +-
 arch/sparc/kernel/pmc.c      |    2 +-
 arch/sparc/kernel/smp_32.c   |   10 +++++++---
 arch/sparc/kernel/time_32.c  |    2 +-
 arch/sparc/lib/checksum_32.S |   12 +++++++++---
 5 files changed, 19 insertions(+), 9 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/