linux-kernel - Re: [PATCH 1/1] sparc: fix accurate exception reporting in copy_{from_to}

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-prev] [day] [month] [year] [list]

Message-ID: <e06f1fba-cf85-4f12-ac1d-1c1b161da9b6@gaisler.com>
Date: Thu, 4 Sep 2025 16:19:29 +0200
From: Andreas Larsson <andreas@...sler.com>
To: Michael Karcher <kernel@...rcher.dialup.fu-berlin.de>,
 linux-kernel@...r.kernel.org
Cc: sparclinux@...r.kernel.org,
 John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
 Anthony Yznaga <anthony.yznaga@...cle.com>
Subject: Re: [PATCH 1/1] sparc: fix accurate exception reporting in
 copy_{from_to}_user for M7

On 2025-08-28 14:18, Michael Karcher wrote:
> ---
>  arch/sparc/lib/M7memcpy.S     | 20 ++++++++++----------
>  arch/sparc/lib/Memcpy_utils.S |  9 +++++++++
>  2 files changed, 19 insertions(+), 10 deletions(-)

I think putting this patch together with the first four in the v2 of the
"Fix accurate exception reporting in SPARC assembly" series would be
good so that they all are under the same cover letter that has the
larger context. A lore link in the v2 letter to both these v1 threads
would allow tracking back the discussion history for both threads.

Cheers,
Andreas