From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Fabian_Bl=C3=A4se_=3Cfabian=40blaese=2Ede=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
Jason@zx2c4.com, fw@strlen.de
Subject: Re: [PATCH v3] icmp: fix icmp_ndo_send address translation for reply direction
Date: Mon, 01 Sep 2025 20:20:12 +0000 [thread overview]
Message-ID: <175675801224.3872744.8064607447852052673.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250828091435.161962-1-fabian@blaese.de>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 28 Aug 2025 11:14:35 +0200 you wrote:
> The icmp_ndo_send function was originally introduced to ensure proper
> rate limiting when icmp_send is called by a network device driver,
> where the packet's source address may have already been transformed
> by SNAT.
>
> However, the original implementation only considers the
> IP_CT_DIR_ORIGINAL direction for SNAT and always replaced the packet's
> source address with that of the original-direction tuple. This causes
> two problems:
>
> [...]
Here is the summary with links:
- [v3] icmp: fix icmp_ndo_send address translation for reply direction
https://git.kernel.org/netdev/net/c/c6dd1aa2cbb7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-09-01 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 20:17 [PATCH] icmp: fix icmp_ndo_send address translation for reply direction Fabian Bläse
2025-08-25 20:38 ` [PATCH v2] " Fabian Bläse
2025-08-27 9:05 ` Florian Westphal
2025-08-27 17:12 ` Fabian Bläse
2025-08-27 17:25 ` Florian Westphal
2025-08-28 9:14 ` [PATCH v3] " Fabian Bläse
2025-08-28 12:00 ` Pablo Neira Ayuso
2025-08-28 12:15 ` Florian Westphal
2025-08-28 12:33 ` Pablo Neira Ayuso
2025-08-28 12:48 ` Florian Westphal
2025-08-28 12:48 ` Florian Westphal
2025-09-01 20: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=175675801224.3872744.8064607447852052673.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Fabian_Bl=C3=A4se_=3Cfabian=40blaese=2Ede=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=Jason@zx2c4.com \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).