From: patchwork-bot+netdevbpf@kernel.org
To: Oscar Maes <oscmaes92@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, dsahern@kernel.org,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] net: ipv4: fix incorrect MTU in broadcast routes
Date: Tue, 15 Jul 2025 00:40:20 +0000 [thread overview]
Message-ID: <175254002050.4040142.7007853567795246386.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250710142714.12986-1-oscmaes92@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 10 Jul 2025 16:27:13 +0200 you wrote:
> Currently, __mkroute_output overrules the MTU value configured for
> broadcast routes.
>
> This buggy behaviour can be reproduced with:
>
> ip link set dev eth1 mtu 9000
> ip route del broadcast 192.168.0.255 dev eth1 proto kernel scope link src 192.168.0.2
> ip route add broadcast 192.168.0.255 dev eth1 proto kernel scope link src 192.168.0.2 mtu 1500
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: ipv4: fix incorrect MTU in broadcast routes
https://git.kernel.org/netdev/net-next/c/9e30ecf23b1b
- [net-next,v2,2/2] selftests: net: add test for variable PMTU in broadcast routes
https://git.kernel.org/netdev/net-next/c/5777d1871bf6
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-07-15 0:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 14:27 [PATCH net-next v2 1/2] net: ipv4: fix incorrect MTU in broadcast routes Oscar Maes
2025-07-10 14:27 ` [PATCH net-next v2 2/2] selftests: net: add test for variable PMTU " Oscar Maes
2025-07-10 14:29 ` [PATCH net-next v2 1/2] net: ipv4: fix incorrect MTU " kernel test robot
2025-07-15 0:40 ` 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=175254002050.4040142.7007853567795246386.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oscmaes92@gmail.com \
--cc=pabeni@redhat.com \
--cc=stable@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