From: patchwork-bot+netdevbpf@kernel.org
To: Ayushman Rout <ayushmanrout27@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
davem@davemloft.net, kuba@kernel.org, hawk@kernel.org,
john.fastabend@gmail.com, sdf@fomichev.me,
netdev@vger.kernel.org
Subject: Re: [PATCH bpf v2 0/2] bpf: Fix overlapping copies in bpf_dynptr_copy()
Date: Sun, 01 Nov 2026 01:20:05 +0000 [thread overview]
Message-ID: <179349600580.2297828.9362269929771966458.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261026162810.12862-1-ayushmanrout27@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 26 Oct 2026 21:58:07 +0530 you wrote:
> bpf_dynptr_copy() can corrupt data when both ranges are in the same xdp
> packet and overlap: a slice of one range is used as the buffer for
> __bpf_dynptr_read() or __bpf_dynptr_write(), and the chunk loop always
> copies forward.
>
> Patch 1 does not use a slice as the buffer for a copy within one packet
> and copies from the end when the destination is above the source.
> Patch 2 adds selftests. They pass with the fix.
>
> [...]
Here is the summary with links:
- [bpf,v2,1/2] bpf: Fix bpf_dynptr_copy() for overlapping ranges in one packet
https://git.kernel.org/bpf/bpf/c/696f0954e3b6
- [bpf,v2,2/2] selftests/bpf: Test overlapping dynptr copies on xdp frags
https://git.kernel.org/bpf/bpf/c/8f92b56d228d
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-11-01 1:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 16:28 [PATCH bpf v2 0/2] bpf: Fix overlapping copies in bpf_dynptr_copy() Ayushman Rout
2026-10-26 16:28 ` [PATCH bpf v2 1/2] bpf: Fix bpf_dynptr_copy() for overlapping ranges in one packet Ayushman Rout
2026-10-26 16:41 ` sashiko-bot
2026-10-26 16:28 ` [PATCH bpf v2 2/2] selftests/bpf: Test overlapping dynptr copies on xdp frags Ayushman Rout
2026-11-01 1:20 ` 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=179349600580.2297828.9362269929771966458.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=ayushmanrout27@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
/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.