[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <163537620786.14362.5033693418821355895.git-patchwork-notify@kernel.org>
Date: Wed, 27 Oct 2021 23:10:07 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: tongtiangen <tongtiangen@...wei.com>
Cc: paul.walmsley@...ive.com, palmer@...belt.com,
palmerdabbelt@...gle.com, aou@...s.berkeley.edu, bjorn@...nel.org,
luke.r.nels@...il.com, xi.wang@...il.com, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org, kafai@...com,
songliubraving@...com, yhs@...com, john.fastabend@...il.com,
kpsingh@...nel.org, linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
bpf@...r.kernel.org
Subject: Re: [PATCH bpf-next,v3] riscv, bpf: Add BPF exception tables
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@...earbox.net>:
On Wed, 27 Oct 2021 11:18:22 +0000 you wrote:
> When a tracing BPF program attempts to read memory without using the
> bpf_probe_read() helper, the verifier marks the load instruction with
> the BPF_PROBE_MEM flag. Since the riscv JIT does not currently recognize
> this flag it falls back to the interpreter.
>
> Add support for BPF_PROBE_MEM, by appending an exception table to the
> BPF program. If the load instruction causes a data abort, the fixup
> infrastructure finds the exception table and fixes up the fault, by
> clearing the destination register and jumping over the faulting
> instruction.
>
> [...]
Here is the summary with links:
- [bpf-next,v3] riscv, bpf: Add BPF exception tables
https://git.kernel.org/bpf/bpf-next/c/252c765bd764
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists