All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ren Wei <weir@nebusec.ai>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, idosch@nvidia.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, vega@nebusec.ai,
	edragain@163.com
Subject: Re: [PATCH net v2 0/1] ipv4: fix a non-progressing fragmentation loop from undersized effective MTUs
Date: Tue, 18 Aug 2026 16:50:11 +0000	[thread overview]
Message-ID: <178707181138.2177226.3831594086427504955.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1786599079.git.edragain@163.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 14 Aug 2026 01:35:25 +0800 you wrote:
> From: Yong Wang <edragain@163.com>
> 
> Hi Linux kernel maintainers,
> 
> This series fixes a non-progressing IPv4 fragmentation loop in
> net/ipv4/ip_output.c. The bug is reachable by a non-root user with
> CAP_NET_ADMIN in a user-created user and network namespace.
> 
> [...]

Here is the summary with links:
  - [net,v2,1/1] ipv4: reject undersized MTUs in ip_do_fragment()
    https://git.kernel.org/netdev/net/c/c0726f0caf8c

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



      parent reply	other threads:[~2026-08-18 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 17:35 [PATCH net v2 0/1] ipv4: fix a non-progressing fragmentation loop from undersized effective MTUs Ren Wei
2026-08-13 17:35 ` [PATCH net v2 1/1] ipv4: reject undersized MTUs in ip_do_fragment() Ren Wei
2026-08-16 10:44   ` Ido Schimmel
2026-08-18 16:50 ` 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=178707181138.2177226.3831594086427504955.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edragain@163.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vega@nebusec.ai \
    --cc=weir@nebusec.ai \
    /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.