From: patchwork-bot+netdevbpf@kernel.org
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: ttoukan.linux@gmail.com, borkmann@iogearbox.net, ast@kernel.org,
andrii.nakryiko@gmail.com, bpf@vger.kernel.org,
tariqt@nvidia.com, gal@nvidia.com, lorenzo@kernel.org,
netdev@vger.kernel.org, andrew.gospodarek@broadcom.com
Subject: Re: [PATCH bpf-next] samples/bpf: xdp1 and xdp2 reduce XDPBUFSIZE to 60
Date: Wed, 31 May 2023 11:10:21 +0000 [thread overview]
Message-ID: <168553142118.8778.13734140798263621950.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <168545704139.2996228.2516528552939485216.stgit@firesoul>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 30 May 2023 16:30:41 +0200 you wrote:
> Default samples/pktgen scripts send 60 byte packets as hardware
> adds 4-bytes FCS checksum, which fulfils minimum Ethernet 64 bytes
> frame size.
>
> XDP layer will not necessary have access to the 4-bytes FCS checksum.
>
> This leads to bpf_xdp_load_bytes() failing as it tries to copy
> 64-bytes from an XDP packet that only have 60-bytes available.
>
> [...]
Here is the summary with links:
- [bpf-next] samples/bpf: xdp1 and xdp2 reduce XDPBUFSIZE to 60
https://git.kernel.org/bpf/bpf-next/c/60548b825b08
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:[~2023-05-31 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 14:30 [PATCH bpf-next] samples/bpf: xdp1 and xdp2 reduce XDPBUFSIZE to 60 Jesper Dangaard Brouer
2023-05-31 7:23 ` Tariq Toukan
2023-05-31 9:38 ` Jesper Dangaard Brouer
2023-05-31 11: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=168553142118.8778.13734140798263621950.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=borkmann@iogearbox.net \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=gal@nvidia.com \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tariqt@nvidia.com \
--cc=ttoukan.linux@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).