From: patchwork-bot+netdevbpf@kernel.org
To: Florian Westphal <fw@strlen.de>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev, daniel@iogearbox.net,
netdev@vger.kernel.org,
syzbot+0c4150bff9fff3bf023c@syzkaller.appspotmail.com,
edumazet@google.com
Subject: Re: [PATCH bpf] bpf: avoid splat in pskb_pull_reason
Date: Fri, 14 Jun 2024 15:30:30 +0000 [thread overview]
Message-ID: <171837903059.8969.17261138323063584002.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240614101801.9496-1-fw@strlen.de>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 14 Jun 2024 12:17:33 +0200 you wrote:
> syzkaller builds (CONFIG_DEBUG_NET=y) frequently trigger a debug
> hint in pskb_may_pull.
>
> We'd like to retain this debug check because it might hint at integer
> overflows and other issues (kernel code should pull headers, not huge
> value).
>
> [...]
Here is the summary with links:
- [bpf] bpf: avoid splat in pskb_pull_reason
https://git.kernel.org/bpf/bpf/c/2bbe3e5a2f4e
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:[~2024-06-14 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 22:15 [Patch net] net: remove the bogus overflow debug check in pskb_may_pull() Cong Wang
2024-06-06 23:27 ` Florian Westphal
2024-06-07 16:14 ` Cong Wang
2024-06-07 21:32 ` Kuniyuki Iwashima
2024-06-08 8:01 ` Eric Dumazet
2024-06-08 22:24 ` Florian Westphal
2024-06-09 2:01 ` Jason Xing
2024-06-14 10:17 ` [PATCH bpf] bpf: avoid splat in pskb_pull_reason Florian Westphal
2024-06-14 12:11 ` Eric Dumazet
2024-06-14 15:30 ` 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=171837903059.8969.17261138323063584002.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=syzbot+0c4150bff9fff3bf023c@syzkaller.appspotmail.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).