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, andrii@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
eric.dumazet@gmail.com, syzkaller@googlegroups.com
Subject: Re: [PATCH] bpf: make sure mac_header was set before using it
Date: Thu, 07 Jul 2022 18:20:13 +0000 [thread overview]
Message-ID: <165721801302.2116.12763817658962623961.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220707123900.945305-1-edumazet@google.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 7 Jul 2022 12:39:00 +0000 you wrote:
> Classic BPF has a way to load bytes starting from the mac header.
>
> Some skbs do not have a mac header, and skb_mac_header()
> in this case is returning a pointer that 65535 bytes after
> skb->head.
>
> Existing range check in bpf_internal_load_pointer_neg_helper()
> was properly kicking and no illegal access was happening.
>
> [...]
Here is the summary with links:
- bpf: make sure mac_header was set before using it
https://git.kernel.org/bpf/bpf/c/0326195f523a
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:[~2022-07-07 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 12:39 [PATCH] bpf: make sure mac_header was set before using it Eric Dumazet
2022-07-07 18:20 ` patchwork-bot+netdevbpf [this message]
2022-07-07 18:31 ` Alexei Starovoitov
2022-07-07 18:36 ` Eric Dumazet
2022-07-07 18:40 ` Alexei Starovoitov
2022-07-07 21:04 ` Daniel Borkmann
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=165721801302.2116.12763817658962623961.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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller@googlegroups.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).