From: patchwork-bot+linux-riscv@kernel.org
To: Jiakai Xu <xujiakai2025@iscas.ac.cn>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr
Subject: Re: [PATCH] riscv: fix KUnit test_kprobes crash when building with Clang
Date: Tue, 18 Nov 2025 21:10:06 +0000 [thread overview]
Message-ID: <176350020601.107040.11107481063131257896.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <738dd4e2.ff73.19a7cd7b4d5.Coremail.xujiakai2025@iscas.ac.cn>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Paul Walmsley <pjw@kernel.org>:
On Thu, 13 Nov 2025 18:51:42 +0800 (GMT+08:00) you wrote:
> Clang misaligns the test_kprobes_addresses and test_kprobes_functions
> arrays, or does not export local labels by default. Both can cause
> kmalloc_array() allocation errors and KUnit failures.
>
> This patch fixes the issue by:
> - Adding .section .rodata to explicitly place arrays in the read-only data segment.
> - Adding .align 3 to align arrays to 8 bytes.
> - Adding .globl to probe labels to ensure symbols are visible.
>
> [...]
Here is the summary with links:
- riscv: fix KUnit test_kprobes crash when building with Clang
https://git.kernel.org/riscv/c/e2285bd4a467
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Jiakai Xu <xujiakai2025@iscas.ac.cn>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr
Subject: Re: [PATCH] riscv: fix KUnit test_kprobes crash when building with Clang
Date: Tue, 18 Nov 2025 21:10:06 +0000 [thread overview]
Message-ID: <176350020601.107040.11107481063131257896.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <738dd4e2.ff73.19a7cd7b4d5.Coremail.xujiakai2025@iscas.ac.cn>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Paul Walmsley <pjw@kernel.org>:
On Thu, 13 Nov 2025 18:51:42 +0800 (GMT+08:00) you wrote:
> Clang misaligns the test_kprobes_addresses and test_kprobes_functions
> arrays, or does not export local labels by default. Both can cause
> kmalloc_array() allocation errors and KUnit failures.
>
> This patch fixes the issue by:
> - Adding .section .rodata to explicitly place arrays in the read-only data segment.
> - Adding .align 3 to align arrays to 8 bytes.
> - Adding .globl to probe labels to ensure symbols are visible.
>
> [...]
Here is the summary with links:
- riscv: fix KUnit test_kprobes crash when building with Clang
https://git.kernel.org/riscv/c/e2285bd4a467
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-11-18 21:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 10:51 [PATCH] riscv: fix KUnit test_kprobes crash when building with Clang 许佳凯
2025-11-13 10:51 ` 许佳凯
2025-11-16 5:15 ` Paul Walmsley
2025-11-16 5:15 ` Paul Walmsley
2025-11-17 3:03 ` Jiakai Xu
2025-11-17 3:03 ` Jiakai Xu
2025-11-18 20:21 ` Paul Walmsley
2025-11-18 20:21 ` Paul Walmsley
2025-11-19 1:38 ` Nathan Chancellor
2025-11-19 1:38 ` Nathan Chancellor
2025-11-19 3:33 ` Jiakai Xu
2025-11-19 3:33 ` Jiakai Xu
2025-11-19 3:01 ` Jiakai Xu
2025-11-19 3:01 ` Jiakai Xu
2025-11-22 1:10 ` Paul Walmsley
2025-11-22 1:10 ` Paul Walmsley
2025-12-26 3:31 ` Jiakai Xu
2025-12-26 3:31 ` Jiakai Xu
2025-11-18 21:10 ` patchwork-bot+linux-riscv [this message]
2025-11-18 21:10 ` patchwork-bot+linux-riscv
2025-11-26 9:23 ` Nam Cao
2025-11-26 9:23 ` Nam Cao
2025-11-26 18:08 ` Nam Cao
2025-11-26 18:08 ` Nam Cao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=176350020601.107040.11107481063131257896.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=xujiakai2025@iscas.ac.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.