From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: bpf@vger.kernel.org, ihor.solodrai@linux.dev, andrii@kernel.org,
eddyz87@gmail.com, ast@kernel.org, daniel@iogearbox.net,
memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org, emil@etsalapatis.com,
shuah@kernel.org, axboe@kernel.dk,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf v1] selftests/bpf: Fix test_maps sockmap failure
Date: Wed, 01 Jul 2026 20:10:08 +0000 [thread overview]
Message-ID: <178293660813.1278318.4274170682804829324.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260701071501.39628-1-jiayuan.chen@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 1 Jul 2026 15:14:22 +0800 you wrote:
> test_maps fails in the sockmap test because sockmap_verdict_prog.c
> drops the packet when the first 8 bytes are not directly accessible:
> if (data + 8 > data_end)
> return SK_DROP;
>
> The blamed commit removed bpf_skb_pull_data() from the stream parser
> program so that the parser no longer modifies the skb. That was needed,
> but it also removed an implicit side effect: bpf_skb_pull_data()
> linearized enough of the skb for later direct packet access.
>
> [...]
Here is the summary with links:
- [bpf,v1] selftests/bpf: Fix test_maps sockmap failure
https://git.kernel.org/bpf/bpf-next/c/27a0f3635d86
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-07-01 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 7:14 [PATCH bpf v1] selftests/bpf: Fix test_maps sockmap failure Jiayuan Chen
2026-07-01 20:10 ` 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=178293660813.1278318.4274170682804829324.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jiayuan.chen@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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