All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: netdev@vger.kernel.org, jiayuan.chen@shopee.com,
	syzbot+e738404dcd14b620923c@syzkaller.appspotmail.com,
	davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v4] xfrm: fix ip_rt_bug race in icmp_route_lookup reverse path
Date: Tue, 10 Feb 2026 14:20:06 +0000	[thread overview]
Message-ID: <177073320633.3529986.460622729645384413.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260206050220.59642-1-jiayuan.chen@linux.dev>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri,  6 Feb 2026 13:02:19 +0800 you wrote:
> From: Jiayuan Chen <jiayuan.chen@shopee.com>
> 
> icmp_route_lookup() performs multiple route lookups to find a suitable
> route for sending ICMP error messages, with special handling for XFRM
> (IPsec) policies.
> 
> The lookup sequence is:
> 1. First, lookup output route for ICMP reply (dst = original src)
> 2. Pass through xfrm_lookup() for policy check
> 3. If blocked (-EPERM) or dst is not local, enter "reverse path"
> 4. In reverse path, call xfrm_decode_session_reverse() to get fl4_dec
>    which reverses the original packet's flow (saddr<->daddr swapped)
> 5. If fl4_dec.saddr is local (we are the original destination), use
>    __ip_route_output_key() for output route lookup
> 6. If fl4_dec.saddr is NOT local (we are a forwarding node), use
>    ip_route_input() to simulate the reverse packet's input path
> 7. Finally, pass rt2 through xfrm_lookup() with XFRM_LOOKUP_ICMP flag
> 
> [...]

Here is the summary with links:
  - [net,v4] xfrm: fix ip_rt_bug race in icmp_route_lookup reverse path
    https://git.kernel.org/netdev/net/c/81b84de32bb2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-02-10 14:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06  5:02 [PATCH net v4] xfrm: fix ip_rt_bug race in icmp_route_lookup reverse path Jiayuan Chen
2026-02-10 14:20 ` 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=177073320633.3529986.460622729645384413.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horms@kernel.org \
    --cc=jiayuan.chen@linux.dev \
    --cc=jiayuan.chen@shopee.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+e738404dcd14b620923c@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 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.