mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xia Yan <yanxia@cmss.chinamobile.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	tpluszz77@gmail.com, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, yana06070@163.com
Subject: Re: [PATCH net] ipv6: fix device binding after failed datagram connect
Date: Tue, 03 Nov 2026 21:20:12 +0000	[thread overview]
Message-ID: <179374081204.1885738.206457161503439442.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261029135822.448299-1-yanxia@cmss.chinamobile.com>

Hello:

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

On Thu, 29 Oct 2026 21:58:22 +0800 you wrote:
> __ip6_datagram_connect() can change sk_bound_dev_if when connecting to
> an address that needs a scope ID. If ip6_datagram_dst_update() fails,
> the old peer address and port are restored, but the new device binding
> is left behind.
> 
> A UDP socket can then keep reporting its original peer while sends and
> attempts to reconnect to that peer fail with ENETUNREACH. Replies to the
> socket are also dropped by the device match. The same problem occurs
> when a scoped multicast destination picks up np->mcast_oif.
> 
> [...]

Here is the summary with links:
  - [net] ipv6: fix device binding after failed datagram connect
    https://git.kernel.org/netdev/net/c/bc53aab4881a

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



      reply	other threads:[~2026-11-03 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 13:58 Xia Yan
2026-11-03 21: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=179374081204.1885738.206457161503439442.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tpluszz77@gmail.com \
    --cc=yana06070@163.com \
    --cc=yanxia@cmss.chinamobile.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
all inboxes | Powered by JetHome®