summaryrefslogtreecommitdiff
path: root/tools/lib/bpf
diff options
context:
space:
mode:
authorJiayuan Chen <jiayuan.chen@linux.dev>2026-07-01 15:14:22 +0800
committerAndrii Nakryiko <andrii@kernel.org>2026-07-01 13:06:04 -0700
commit27a0f3635d862919dd7e5e93e19f3f5d1b240e57 (patch)
tree7714216d43a05dce5757ccc60872bc95356db9bb /tools/lib/bpf
parent475b59db3bd5c7717b5441481ac06f226815cb0a (diff)
downloadlinux-next-27a0f3635d862919dd7e5e93e19f3f5d1b240e57.tar.gz
linux-next-27a0f3635d862919dd7e5e93e19f3f5d1b240e57.zip
selftests/bpf: Fix test_maps sockmap failure
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. In this test, the send side goes through the sockmap SK_MSG path. The skb can have skb->len == 20 while its linear area is empty, so the verdict program sees data == data_end and drops the packet even though the payload length is sufficient. Keep the parser read-only, and pull the first 8 bytes in the verdict program before reading or writing them. Reload data/data_end after bpf_skb_pull_data() as required. Fixes: 22a0cc10dacb ("selftests/bpf: don't modify the skb in the strparser parser prog") Reported-by: Ihor Solodrai <ihor.solodrai@linux.dev> Signed-off-by: Jiayuan Chen <jiayuan.chen@linux.dev> Signed-off-by: Andrii Nakryiko <andrii@kernel.org> Link: https://lore.kernel.org/bpf/20260701071501.39628-1-jiayuan.chen@linux.dev Closes: https://lore.kernel.org/bpf/e3a91acd-2b4d-4e93-a3bb-a0e9ee5ede0f@linux.dev/
Diffstat (limited to 'tools/lib/bpf')
0 files changed, 0 insertions, 0 deletions