From: Chenghao Duan <duanchenghao@kylinos.cn>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: yangtiezhu@loongson.cn, hengqi.chen@gmail.com, kernel@xen0n.name,
zhangtianyang@loongson.cn, masahiroy@kernel.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
bpf@vger.kernel.org, youling.tang@linux.dev,
jianghaoran@kylinos.cn, vincent.mc.li@gmail.com
Subject: Re: [PATCH v2 4/4] LoongArch: BPF: Enable BPF exception fixup for specific ADE subcode
Date: Mon, 15 Dec 2025 10:18:22 +0800 [thread overview]
Message-ID: <20251215021822.GA141785@chenghao-pc> (raw)
In-Reply-To: <CAAhV-H5-AaD9SuRWt5gK4ODVA356EO7byqf-AnXvr_0C+FuUPg@mail.gmail.com>
On Sat, Dec 13, 2025 at 09:16:00PM +0800, Huacai Chen wrote:
> Hi, Chenghao,
>
> On Fri, Dec 12, 2025 at 5:11 PM Chenghao Duan <duanchenghao@kylinos.cn> wrote:
> >
> > This patch allows the LoongArch BPF JIT to handle recoverable memory
> > access errors generated by BPF_PROBE_MEM* instructions.
> >
> > When a BPF program performs memory access operations, the instructions
> > it executes may trigger ADEM exceptions. The kernel’s built-in BPF
> > exception table mechanism (EX_TYPE_BPF) will generate corresponding
> > exception fixup entries in the JIT compilation phase; however, the
> > architecture-specific trap handling function needs to proactively call
> > the common fixup routine to achieve exception recovery.
> >
> > do_ade(): fix EX_TYPE_BPF memory access exceptions for BPF programs,
> > ensure safe execution.
> >
> > Signed-off-by: Chenghao Duan <duanchenghao@kylinos.cn>
> > ---
> > arch/loongarch/kernel/traps.c | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/loongarch/kernel/traps.c b/arch/loongarch/kernel/traps.c
> > index da5926fead4a..4cf72e0af6a3 100644
> > --- a/arch/loongarch/kernel/traps.c
> > +++ b/arch/loongarch/kernel/traps.c
> > @@ -534,7 +534,13 @@ asmlinkage void noinstr do_fpe(struct pt_regs *regs, unsigned long fcsr)
> >
> > asmlinkage void noinstr do_ade(struct pt_regs *regs)
> > {
> > - irqentry_state_t state = irqentry_enter(regs);
> > + irqentry_state_t state;
> > + unsigned int esubcode = FIELD_GET(CSR_ESTAT_ESUBCODE, regs->csr_estat);
> > +
> > + if ((esubcode == EXSUBCODE_ADEM) && fixup_exception(regs))
> > + return;
> No chance for ADEF? And I don't think ixup_exception() can be done out
> of irqentry_enter().
At present, exception fixes are only applied to memory-type BPF programs,
with no handling implemented for ADEF.
In the next version, fixup_exception will be processed internally within
irqentry_enter()/irqentry_exit, and the title will be revised with
reference to your suggestions.
Chenghao
>
> This patch is needed by BPF but not part of BPF, so I think the
> subject should be:
> LoongArch: Enable exception fixup for specific ADE subcode
>
> Huacai
>
> > +
> > + state = irqentry_enter(regs);
> >
> > die_if_kernel("Kernel ade access", regs);
> > force_sig_fault(SIGBUS, BUS_ADRERR, (void __user *)regs->csr_badvaddr);
> > --
> > 2.25.1
> >
prev parent reply other threads:[~2025-12-15 2:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 9:10 [PATCH v2 0/4] Fix the failure issue of the module_attach test case Chenghao Duan
2025-12-12 9:11 ` [PATCH v2 1/4] LoongArch: ftrace: Refactor register restoration in ftrace_common_return Chenghao Duan
2025-12-12 9:11 ` [PATCH v2 2/4] ftrace: samples: Adjust register stack restore order in direct call trampolines Chenghao Duan
2025-12-12 9:11 ` [PATCH v2 3/4] LoongArch: BPF: Enhance trampoline support for kernel and module tracing Chenghao Duan
2025-12-14 12:36 ` Tiezhu Yang
2025-12-15 2:32 ` Chenghao Duan
2025-12-12 9:11 ` [PATCH v2 4/4] LoongArch: BPF: Enable BPF exception fixup for specific ADE subcode Chenghao Duan
2025-12-13 13:16 ` Huacai Chen
2025-12-15 2:18 ` Chenghao Duan [this message]
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=20251215021822.GA141785@chenghao-pc \
--to=duanchenghao@kylinos.cn \
--cc=bpf@vger.kernel.org \
--cc=chenhuacai@kernel.org \
--cc=hengqi.chen@gmail.com \
--cc=jianghaoran@kylinos.cn \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=vincent.mc.li@gmail.com \
--cc=yangtiezhu@loongson.cn \
--cc=youling.tang@linux.dev \
--cc=zhangtianyang@loongson.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox