[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4a2312d1-5294-4621-8276-b7a9447b3e1a@iscas.ac.cn>
Date: Mon, 20 Oct 2025 20:59:38 +0800
From: Vivian Wang <wangruikang@...as.ac.cn>
To: Paul Walmsley <pjw@...nel.org>, Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Alexandre Ghiti <alex@...ti.fr>,
Nam Cao <namcao@...utronix.de>
Cc: linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
Han Gao <rabenda.cn@...il.com>, Icenowy Zheng <uwu@...nowy.me>,
Inochi Amaoto <inochiama@...il.com>, Yao Zi <ziyao@...root.org>
Subject: Re: [PATCH 0/2] riscv: tests: Make RISCV_KPROBES_KUNIT tristate
On 10/20/25 20:23, Vivian Wang wrote:
> Fix an allmodconfig warning on v6.18-rc1:
>
> WARNING: 3 bad relocations
> ffffffff81e24118 R_RISCV_64 kunit_unary_assert_format
> ffffffff81e24a60 R_RISCV_64 kunit_binary_assert_format
> ffffffff81e269d0 R_RISCV_JUMP_SLOT __kunit_do_failed_assertion
For more context, I said this was to fix a warning, but I tried it out
anyway just to see what happens. Apparently, nothing. The kprobe tests
just don't run if RISCV_KPROBES_KUNIT=y but KUNIT=m.
So this config combination being just wrong is the problem, and the
warning is just a loud symptom.
Vivian "dramforever" Wang
Powered by blists - more mailing lists