All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, dsahern@kernel.org,
	edumazet@google.com, kuba@kernel.org, horms@kernel.org,
	fred.cc@alibaba-inc.com, cambda@linux.alibaba.com,
	willemb@google.com, lulie@linux.alibaba.com, sbrivio@redhat.com
Subject: Re: [PATCH net] udp: fix l4 hash after reconnect
Date: Tue, 10 Dec 2024 14:40:29 +0000	[thread overview]
Message-ID: <173384162989.835489.4988486681580985293.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <4761e466ab9f7542c68cdc95f248987d127044d2.1733499715.git.pabeni@redhat.com>

Hello:

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

On Fri,  6 Dec 2024 16:49:14 +0100 you wrote:
> After the blamed commit below, udp_rehash() is supposed to be called
> with both local and remote addresses set.
> 
> Currently that is already the case for IPv6 sockets, but for IPv4 the
> destination address is updated after rehashing.
> 
> Address the issue moving the destination address and port initialization
> before rehashing.
> 
> [...]

Here is the summary with links:
  - [net] udp: fix l4 hash after reconnect
    https://git.kernel.org/netdev/net/c/51a00be6a099

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



  parent reply	other threads:[~2024-12-10 14:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 15:49 [PATCH net] udp: fix l4 hash after reconnect Paolo Abeni
2024-12-06 15:57 ` Eric Dumazet
2024-12-06 16:01   ` Eric Dumazet
2024-12-06 16:23     ` Paolo Abeni
2024-12-07  2:34       ` Philo Lu
2024-12-10  8:32         ` Paolo Abeni
2024-12-10 10:45           ` Philo Lu
2024-12-31  7:55           ` Philo Lu
2025-01-07  7:56             ` Paolo Abeni
2025-01-08 12:25               ` Philo Lu
2024-12-10 14:40 ` patchwork-bot+netdevbpf [this message]
2024-12-11  0:59 ` Jakub Kicinski
2024-12-17 12:16   ` Philo Lu

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=173384162989.835489.4988486681580985293.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=cambda@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=fred.cc@alibaba-inc.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=lulie@linux.alibaba.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sbrivio@redhat.com \
    --cc=willemb@google.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.