From: patchwork-bot+netdevbpf@kernel.org
To: Rong Tao <rtoax@foxmail.com>
Cc: vmalik@redhat.com, andrii.nakryiko@gmail.com, ast@kernel.org,
daniel@iogearbox.net, rongtao@cestc.cn, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, mykolal@fb.com, shuah@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v5 0/2] Fix bpf_strnstr len error
Date: Fri, 29 Aug 2025 19:00:08 +0000 [thread overview]
Message-ID: <175649400852.2313311.339778074846590009.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_E72A37AF03A3B18853066E421B5969976208@qq.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sat, 30 Aug 2025 00:30:16 +0800 you wrote:
> From: Rong Tao <rongtao@cestc.cn>
>
> Fix bpf_strnstr() wrong 'len' parameter, bpf_strnstr("open", "open", 4)
> should return 0 instead of -ENOENT. And fix a more general case when s2
> is a suffix of the first len characters of s1.
>
> Rong Tao (2):
> bpf/helpers: bpf_strnstr: Exact match length
> selftests/bpf: Add tests for bpf_strnstr
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/2] bpf/helpers: bpf_strnstr: Exact match length
(no matching commit)
- [bpf-next,v5,2/2] selftests/bpf: Add tests for bpf_strnstr
https://git.kernel.org/bpf/bpf/c/19139f45999a
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:[~2025-08-29 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 16:30 Rong Tao
2025-08-29 19:00 ` 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=175649400852.2313311.339778074846590009.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--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=mykolal@fb.com \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=vmalik@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®