From: patchwork-bot+netdevbpf@kernel.org
To: Ayushman Rout <ayushmanrout27@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, sdf@fomichev.me, martin.lau@linux.dev,
ast@kernel.org, andrii@kernel.org, eddyz87@gmail.com,
memxor@gmail.com, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, hawk@kernel.org,
drosen@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] bpf: Use memmove() to load bytes from an skb and an xdp_buff
Date: Sat, 24 Oct 2026 04:00:09 +0000 [thread overview]
Message-ID: <179281440907.1452471.10626063487064025333.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261022112312.31563-1-ayushmanrout27@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 22 Oct 2026 16:53:11 +0530 you wrote:
> bpf_dynptr_read() on an skb or xdp dynptr ends in bpf_skb_load_bytes()
> or bpf_xdp_load_bytes(). The destination can be a slice of the same
> packet, so it can overlap the source, which memcpy() does not allow.
> On x86 with FSRM memcpy() copies forward, so a destination above the
> source gets the first bytes repeated:
>
> p = bpf_dynptr_slice_rdwr(&ptr, 8, NULL, 64);
> bpf_dynptr_read(p, 64, &ptr, 0, 0);
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf: Use memmove() to load bytes from an skb and an xdp_buff
https://git.kernel.org/bpf/bpf/c/b93cf2c8a055
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-10-24 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 11:23 Ayushman Rout
2026-10-22 12:05 ` bot+bpf-ci
2026-10-24 4: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=179281440907.1452471.10626063487064025333.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=ayushmanrout27@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=drosen@google.com \
--cc=eddyz87@gmail.com \
--cc=edumazet@kernel.org \
--cc=emil@etsalapatis.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--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
all inboxes | Powered by JetHome®