linux-kernel - Re: Re: Re: [PATCH] riscv: fix KUnit test_kprobes crash when building with Clang

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

Message-ID: <f1ea892e-a07a-5ded-dd6e-3e7ea55fe446@kernel.org>
Date: Fri, 21 Nov 2025 18:10:23 -0700 (MST)
From: Paul Walmsley <pjw@...nel.org>
To: Jiakai Xu <xujiakai2025@...as.ac.cn>
cc: Paul Walmsley <pjw@...nel.org>, Nathan Chancellor <nathan@...nel.org>, 
    linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org, 
    Palmer Dabbelt <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>, 
    Alexandre Ghiti <alex@...ti.fr>, namcao@...utronix.de
Subject: Re: Re: Re: [PATCH] riscv: fix KUnit test_kprobes crash when building
 with Clang

On Wed, 19 Nov 2025, Jiakai Xu wrote:

> &gt; Looks like you're using a mail client that sends HTML in what should be a 
> &gt; plain-text E-mail; please fix that.
> 
> I apologize for that oversight. 
> I will make sure to use plain-text emails going forward.

Looks like there's still a problem (the "&gt;"s above).

> &gt; Not all of it, but some edited summary is appropriate.  I've queued the 
> &gt; following revision for v6.18-rc fixes, under the theory that it would be 
> &gt; good to get the test working for Clang users while the LLVM folks 
> &gt; investigate.  Please let us know ASAP if you think anything in it should 
> &gt; be changed.  I plan to send a PR out later this week.
> 
> Thank you for your review of the patch and for the time and effort
> you spent on it. I fully agree with the modifications you made to the patch
> description.

Looks like some of the LLVM folks have responded to 
https://github.com/llvm/llvm-project/issues/168308 with some suggestions.  
Could you implement those and test it and update the patch?  If that can 
be done by early next week, then we should hopefully be able to get it in 
before v6.18 is tagged.

thanks,

- Paul