linux-kernel - Re: [PATCH 2/4] 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <8403ac15-bb3a-4e88-97ef-6eaff26cc8db@gaisler.com>
Date: Thu, 4 Sep 2025 16:05:04 +0200
From: Andreas Larsson <andreas@...sler.com>
To: Michael Karcher <kernel@...rcher.dialup.fu-berlin.de>,
 Anthony Yznaga <anthony.yznaga@...cle.com>, linux-kernel@...r.kernel.org
Cc: sparclinux@...r.kernel.org,
 John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
Subject: Re: [PATCH 2/4] sparc: fix accurate exception reporting in
 copy_{from_to}_user for UltraSPARC III

On 2025-08-30 10:35, Michael Karcher wrote:
> 
>> I think there should be a little more text about the nature of the failure. Maybe:
> 
> I will add something like that in v2 of the series.
> Do you think it is useful to add the message ID
> b14f55642207e63e907965e209f6323a0df6dcee.camel@...sik.fu-berlin.de
> as well, or an abbreviated backtrace from that message?
> I suppose, that is the BUG_ON you are referring to.

If that is the message referred to, I think it is a good idea to refer
to it, in addition to a description. If so, please do it on the form of
a lore link, like this:

https://lore.kernel.org/r/<message-id>

Cheers,
Andreas