From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net,
kernel-team@cloudflare.com, netdev@vger.kernel.org,
lkp@intel.com
Subject: Re: [PATCH bpf-next v2] bpf: Return an error pointer for skb metadata when CONFIG_NET=n
Date: Fri, 05 Sep 2025 04:40:07 +0000 [thread overview]
Message-ID: <175704720726.2040233.14416715550845676114.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250901-dynptr-skb-meta-no-net-v2-1-ce607fcb6091@cloudflare.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Mon, 01 Sep 2025 15:27:43 +0200 you wrote:
> Kernel Test Robot reported a compiler warning - a null pointer may be
> passed to memmove in __bpf_dynptr_{read,write} when building without
> networking support.
>
> The warning is correct from a static analysis standpoint, but not actually
> reachable. Without CONFIG_NET, creating dynptrs to skb metadata is
> impossible since the constructor kfunc is missing.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf: Return an error pointer for skb metadata when CONFIG_NET=n
https://git.kernel.org/bpf/bpf-next/c/54728bd535fb
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:[~2025-09-05 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 13:27 [PATCH bpf-next v2] bpf: Return an error pointer for skb metadata when CONFIG_NET=n Jakub Sitnicki
2025-09-05 4:40 ` 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=175704720726.2040233.14416715550845676114.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=jakub@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=lkp@intel.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
/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.