From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
daniel@iogearbox.net, ast@kernel.org, martin.lau@linux.dev,
andrii@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org,
eric.dumazet@gmail.com,
syzbot+9e27778c0edc62cb97d8@syzkaller.appspotmail.com,
sdf@google.com, willemb@google.com
Subject: Re: [PATCH net] bpf: Don't redirect too small packets
Date: Fri, 22 Mar 2024 14:10:32 +0000 [thread overview]
Message-ID: <171111663201.19374.16295682760005551863.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240322122407.1329861-1-edumazet@google.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 22 Mar 2024 12:24:07 +0000 you wrote:
> Some drivers ndo_start_xmit() expect a minimal size, as shown
> by various syzbot reports [1].
>
> Willem added in commit 217e6fa24ce2 ("net: introduce device min_header_len")
> the missing attribute that can be used by upper layers.
>
> We need to use it in __bpf_redirect_common().
>
> [...]
Here is the summary with links:
- [net] bpf: Don't redirect too small packets
https://git.kernel.org/bpf/bpf/c/96b0e83341e8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-03-22 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 12:24 [PATCH net] bpf: Don't redirect too small packets Eric Dumazet
2024-03-22 14:10 ` patchwork-bot+netdevbpf [this message]
2024-03-23 3:01 ` Alexei Starovoitov
2024-03-25 13:33 ` Eric Dumazet
2024-03-25 15:47 ` Daniel Borkmann
2024-03-25 15:56 ` Alexei Starovoitov
2024-03-25 16:28 ` Stanislav Fomichev
2024-03-26 12:46 ` Daniel Borkmann
2024-03-26 13:37 ` Eric Dumazet
2024-03-26 13:38 ` Eric Dumazet
2024-03-26 17:57 ` Daniel Borkmann
2024-03-26 18:08 ` Eric Dumazet
2024-09-22 17:39 ` Eric Dumazet
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=171111663201.19374.16295682760005551863.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=syzbot+9e27778c0edc62cb97d8@syzkaller.appspotmail.com \
--cc=willemb@google.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 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.