From: patchwork-bot+netdevbpf@kernel.org
To: Chengkaitao <pilgrimtao@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
shuah@kernel.org, yangfeng@kylinos.cn,
alexei.starovoitov@gmail.com, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
chengkaitao@kylinos.cn
Subject: Re: [PATCH RESEND v7 0/5] bpf: Expand the usage scenarios of bpf_kptr_xchg
Date: Tue, 24 Feb 2026 01:50:12 +0000 [thread overview]
Message-ID: <177189781254.3271663.4849399653338044310.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260214124042.62229-1-pilgrimtao@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 14 Feb 2026 20:40:37 +0800 you wrote:
> From: Kaitao Cheng <chengkaitao@kylinos.cn>
>
> When using bpf_kptr_xchg, we triggered the following error:
> 31: (85) call bpf_kptr_xchg#194
> function calls are not allowed while holding a lock
> bpf_kptr_xchg can now be used in lock-held contexts, so we extended
> its usage scope in [patch 1/5].
>
> [...]
Here is the summary with links:
- [RESEND,v7,1/5] bpf: allow calling bpf_kptr_xchg while holding a lock
https://git.kernel.org/bpf/bpf-next/c/964c0747686a
- [RESEND,v7,2/5] bpf: allow using bpf_kptr_xchg even if the NON_OWN_REF flag is set
https://git.kernel.org/bpf/bpf-next/c/ee9886c40aae
- [RESEND,v7,3/5] selftests/bpf: Add supplementary tests for bpf_kptr_xchg
https://git.kernel.org/bpf/bpf-next/c/580fa3430b5d
- [RESEND,v7,4/5] bpf: allow using bpf_kptr_xchg even if the MEM_RCU flag is set
https://git.kernel.org/bpf/bpf-next/c/fb1590448ff7
- [RESEND,v7,5/5] selftests/bpf: Add test case for rbtree nodes that contain both bpf_refcount and kptr fields.
https://git.kernel.org/bpf/bpf-next/c/ed8fa4b8894f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-02-24 1:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 12:40 [PATCH RESEND v7 0/5] bpf: Expand the usage scenarios of bpf_kptr_xchg Chengkaitao
2026-02-14 12:40 ` [PATCH RESEND v7 1/5] bpf: allow calling bpf_kptr_xchg while holding a lock Chengkaitao
2026-02-14 12:40 ` [PATCH RESEND v7 2/5] bpf: allow using bpf_kptr_xchg even if the NON_OWN_REF flag is set Chengkaitao
2026-02-14 13:09 ` bot+bpf-ci
2026-02-14 12:40 ` [PATCH RESEND v7 3/5] selftests/bpf: Add supplementary tests for bpf_kptr_xchg Chengkaitao
2026-02-14 12:40 ` [PATCH RESEND v7 4/5] bpf: allow using bpf_kptr_xchg even if the MEM_RCU flag is set Chengkaitao
2026-02-14 12:40 ` [PATCH RESEND v7 5/5] selftests/bpf: Add test case for rbtree nodes that contain both bpf_refcount and kptr fields Chengkaitao
2026-02-24 1:50 ` patchwork-bot+netdevbpf [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=177189781254.3271663.4849399653338044310.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chengkaitao@kylinos.cn \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=pilgrimtao@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yangfeng@kylinos.cn \
--cc=yonghong.song@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.