From: Jakub Kicinski <kuba@kernel.org>
To: Kyle Zeng <kylebot@openai.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, outbounddisclosures@openai.com
Subject: Re: [PATCH] mpls: reject headroom that overflows skb header offsets
Date: Mon, 9 Nov 2026 15:08:08 -0800 [thread overview]
Message-ID: <20261109150808.32b625f3@kernel.org> (raw)
In-Reply-To: <20261030042246.74144-1-kylebot@openai.com>
On Thu, 29 Oct 2026 21:22:46 -0700 Kyle Zeng wrote:
> For example, a netkit device with needed_headroom 65488 gives an initial
> network offset of 65504.
We should probably cap the needed_headroom at something reasonable,
then? Also AI review suggests the fix is incomplete.
--
pw-bot: cr
prev parent reply other threads:[~2026-11-09 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 4:22 [PATCH] mpls: reject headroom that overflows skb header offsets Kyle Zeng
2026-10-30 4:29 ` netdev-bot+sinfo
2026-11-03 4:59 ` netdev-bot+sashiko
2026-11-09 23:08 ` Jakub Kicinski [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=20261109150808.32b625f3@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kylebot@openai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=outbounddisclosures@openai.com \
--cc=pabeni@redhat.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.