From: Ido Schimmel <idosch@nvidia.com>
To: Eric Dumazet <edumazet@kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org, Paul Moore <paul@paul-moore.com>,
linux-security-module@vger.kernel.org,
Kyle Zeng <kylebot@openai.com>
Subject: Re: [PATCH net v2 1/2] ipv4: recompile IP options on a private copy in ipv4_send_dest_unreach()
Date: Thu, 12 Nov 2026 15:46:45 +0200 [thread overview]
Message-ID: <20261112134645.GA3195113@shredder> (raw)
In-Reply-To: <20261109131736.3060756-2-edumazet@kernel.org>
On Mon, Nov 09, 2026 at 02:17:35PM +0100, Eric Dumazet wrote:
> diff --git a/net/ipv4/route.c b/net/ipv4/route.c
> index 3a90c8d28b940bf615c165d9b30ac634943586e1..9af72cb892034deff2bb3169911c02c025d73cf2 100644
> --- a/net/ipv4/route.c
> +++ b/net/ipv4/route.c
> @@ -1256,6 +1256,7 @@ EXPORT_INDIRECT_CALLABLE(ipv4_dst_check);
>
> static void ipv4_send_dest_unreach(struct sk_buff *skb)
> {
> + struct sk_buff *nskb = NULL;
> struct inet_skb_parm parm;
> struct net_device *dev;
> int res;
> @@ -1271,6 +1272,16 @@ static void ipv4_send_dest_unreach(struct sk_buff *skb)
> if (ip_hdr(skb)->ihl > 5) {
> if (!pskb_network_may_pull(skb, ip_hdr(skb)->ihl * 4))
> return;
> +
> + /* __ip_options_compile() writes into the options, and
> + * callers of dst_link_failure() may cache pointers into
> + * skb->head: work on a private copy.
> + */
> + nskb = pskb_copy(skb, GFP_ATOMIC);
> + if (!nskb)
> + return;
> + skb = nskb;
> +
> parm.opt.optlen = ip_hdr(skb)->ihl * 4 - sizeof(struct iphdr);
>
> rcu_read_lock();
> @@ -1279,9 +1290,11 @@ static void ipv4_send_dest_unreach(struct sk_buff *skb)
> rcu_read_unlock();
>
> if (res)
> - return;
> + goto out;
> }
> __icmp_send(skb, ICMP_DEST_UNREACH, ICMP_HOST_UNREACH, 0, &parm);
> +out:
> + consume_skb(nskb);
> }
Not sure that what Sashiko describes can happen today, but I wouldn't
rely on the network header not being in the headroom. Something like (on
top of your patch):
diff --git a/net/ipv4/route.c b/net/ipv4/route.c
index 630143ca0f31..77c03620f89d 100644
--- a/net/ipv4/route.c
+++ b/net/ipv4/route.c
@@ -1282,6 +1282,10 @@ static void ipv4_send_dest_unreach(struct sk_buff *skb)
if (!pskb_network_may_pull(skb, ip_hdr(skb)->ihl * 4))
return;
+ /* pskb_copy() does not copy the headroom */
+ if (skb_network_offset(skb) < 0)
+ return;
+
/* __ip_options_compile() writes into the options, and
* callers of dst_link_failure() may cache pointers into
* skb->head: work on a private copy.
next prev parent reply other threads:[~2026-11-12 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 13:17 [PATCH net v2 0/2] ipv4: do not write shared IP options when sending ICMP errors Eric Dumazet
2026-11-09 13:17 ` [PATCH net v2 1/2] ipv4: recompile IP options on a private copy in ipv4_send_dest_unreach() Eric Dumazet
2026-11-10 14:04 ` netdev-bot+sashiko
2026-11-12 13:46 ` Ido Schimmel [this message]
2026-11-09 13:17 ` [PATCH net v2 2/2] cipso: unshare headers before recompiling IP options in cipso_v4_error() Eric Dumazet
2026-11-09 21:43 ` Paul Moore
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=20261112134645.GA3195113@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kylebot@openai.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.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