From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: chenhuacai@kernel.org, hengqi.chen@gmail.com,
loongarch@lists.linux.dev, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] LoongArch: BPF: Make arch_protect_bpf_trampoline() return 0
Date: Thu, 19 Mar 2026 21:24:13 +0000 [thread overview]
Message-ID: <177395545307.1805592.472462208613814092.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260310064706.4985-1-yangtiezhu@loongson.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Huacai Chen <chenhuacai@loongson.cn>:
On Tue, 10 Mar 2026 14:47:06 +0800 you wrote:
> Occasionally, there exists "text_copy_cb: operation failed" when executing
> bpf selftests, the reason is copy_to_kernel_nofault() failed and the ecode
> of estat register is 0x4 (PME: Page Modification Exception) due to the pte
> is not writeable, the root cause is that there is another place to set pte
> readonly which is in the generic weak arch_protect_bpf_trampoline().
>
> There are two ways to fix this race condition issue, the direct way is to
> modify the generic weak arch_protect_bpf_trampoline() to add a mutex lock
> for set_memory_rox(), but the other simple and proper way is to just make
> arch_protect_bpf_trampoline() return 0 in the arch-specific code because
> LoongArch already uses BPF prog pack allocator for trampoline.
>
> [...]
Here is the summary with links:
- [v1] LoongArch: BPF: Make arch_protect_bpf_trampoline() return 0
https://git.kernel.org/netdev/net/c/b254c629a963
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:[~2026-03-19 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 6:47 [PATCH v1] LoongArch: BPF: Make arch_protect_bpf_trampoline() return 0 Tiezhu Yang
2026-03-10 7:29 ` bot+bpf-ci
2026-03-15 3:27 ` Hengqi Chen
2026-03-15 8:04 ` Huacai Chen
2026-03-19 21:24 ` patchwork-bot+netdevbpf [this message]
2026-03-20 3:27 ` Huacai Chen
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=177395545307.1805592.472462208613814092.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenhuacai@kernel.org \
--cc=hengqi.chen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=yangtiezhu@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