linux-kernel - [GIT PULL] MIPS fixes for v6.9

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <Zhjt0hXiftxCyFsH@alpha.franken.de>
Date: Fri, 12 Apr 2024 10:16:18 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: torvalds@...ux-foundation.org
Cc: linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [GIT PULL] MIPS fixes for v6.9

The following changes since commit 4cece764965020c22cff7665b18a012006359095:

  Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_6.9_1

for you to fetch changes up to 4370b673ccf240bf7587b0cb8e6726a5ccaf1f17:

  MIPS: scall: Save thread_info.syscall unconditionally on entry (2024-04-09 16:52:21 +0200)

----------------------------------------------------------------
Fix for syscall_get_nr() to make it work even if tracing is disabled

----------------------------------------------------------------
Jiaxun Yang (1):
      MIPS: scall: Save thread_info.syscall unconditionally on entry

 arch/mips/include/asm/ptrace.h |  2 +-
 arch/mips/kernel/asm-offsets.c |  1 +
 arch/mips/kernel/ptrace.c      | 15 ++++++---------
 arch/mips/kernel/scall32-o32.S | 23 +++++++++++++----------
 arch/mips/kernel/scall64-n32.S |  3 ++-
 arch/mips/kernel/scall64-n64.S |  3 ++-
 arch/mips/kernel/scall64-o32.S | 33 +++++++++++++++++----------------
 7 files changed, 42 insertions(+), 38 deletions(-)

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]