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:	Sun, 19 Oct 2014 13:26:58 -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


Here we have two bug fixes:

1) The current thread's fault_code is not setup properly upon entry to
   do_sparc64_fault() in some paths, leading to spurious SIGBUS.

2) Don't use a zero length array at the end of thread_info on sparc64,
   otherwise end_of_stack() isn't right.

Please pull, thanks!

The following changes since commit 52d589a01d4545ce1dc5c3892bb8c7b55edfe714:

  Merge branch 'for-linus' of git://git.infradead.org/users/vkoul/slave-dma (2014-10-18 18:11:04 -0700)

are available in the git repository at:


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

for you to fetch changes up to e2653143d7d79a49f1a961aeae1d82612838b12c:

  sparc64: Do not define thread fpregs save area as zero-length array. (2014-10-18 23:12:33 -0400)

----------------------------------------------------------------
David S. Miller (2):
      sparc64: Fix corrupted thread fault code.
      sparc64: Do not define thread fpregs save area as zero-length array.

 arch/sparc/include/asm/thread_info_64.h | 3 ++-
 arch/sparc/kernel/dtlb_prot.S           | 6 +++---
 arch/sparc/kernel/tsb.S                 | 6 +++---
 3 files changed, 8 insertions(+), 7 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/