[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87ikn0tpx0.fsf@all.your.base.are.belong.to.us>
Date: Sat, 19 Apr 2025 12:18:51 +0200
From: Björn Töpel <bjorn@...nel.org>
To: Samuel Holland <samuel.holland@...ive.com>, Paul Walmsley
<paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>, Alexandre
Ghiti <alex@...ti.fr>, linux-riscv@...ts.infradead.org, Guo Ren
<guoren@...nel.org>
Cc: Björn Töpel <bjorn@...osinc.com>, Masami Hiramatsu
<mhiramat@...nel.org>, Oleg Nesterov <oleg@...hat.com>, Peter Zijlstra
<peterz@...radead.org>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH fixes] riscv: uprobes: Add missing fence.i after
building the XOL buffer
Samuel Holland <samuel.holland@...ive.com> writes:
> Hi Björn,
>
> On 2025-04-17 2:49 AM, Björn Töpel wrote:
>> From: Björn Töpel <bjorn@...osinc.com>
>>
>> The XOL (execute out-of-line) buffer is used to single-step the
>> replaced instruction(s) for uprobes. The RISC-V port was missing a
>> proper fence.i (i$ flushing) after constructing the XOL buffer, which
>> can result in incorrect execution of stale/broken instructions.
>>
>> This was found running the BPF selftests "test_progs:
>> uprobe_autoattach, attach_probe" on the Spacemit K1/X60, where the
>> uprobes tests randomly blew up.
>>
>> Fixes: 74784081aac8 ("riscv: Add uprobes supported")
>> Signed-off-by: Björn Töpel <bjorn@...osinc.com>
>> ---
>> arch/riscv/kernel/probes/uprobes.c | 9 +--------
>> 1 file changed, 1 insertion(+), 8 deletions(-)
>>
>> diff --git a/arch/riscv/kernel/probes/uprobes.c b/arch/riscv/kernel/probes/uprobes.c
>> index 4b3dc8beaf77..4faef92dd771 100644
>> --- a/arch/riscv/kernel/probes/uprobes.c
>> +++ b/arch/riscv/kernel/probes/uprobes.c
>> @@ -176,13 +176,6 @@ void arch_uprobe_copy_ixol(struct page *page, unsigned long vaddr,
>> *(uprobe_opcode_t *)dst = __BUG_INSN_32;
>> }
>>
>> + flush_icache_range((unsigned long)dst, (unsigned long)dst + len);
>
> This works because flush_icache_range currently ignores the range, but
> semantically is not quite right, because of the line just above the context that
> increments dst. If the range was respected, this would only flush the ebreak,
> not the preceding single-stepped instruction.
Indeed! That was sloppy! I'll spin a v2!
Thank you!
Björn
Powered by blists - more mailing lists