netdev - Re: [PATCH net v2 0/2] add drop reason when do fragment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANn89i+khPeMERP6nVi21M=NH4v8sy3zASqAnZDs9FuryFsJtA@mail.gmail.com>
Date: Fri, 24 Oct 2025 04:25:32 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Yonglong Li <liyonglong@...natelecom.cn>
Cc: netdev@...r.kernel.org, davem@...emloft.net, dsahern@...nel.org, 
	pabeni@...hat.com, kuba@...nel.org, horms@...nel.org
Subject: Re: [PATCH net v2 0/2] add drop reason when do fragment

On Fri, Oct 24, 2025 at 3:20 AM Yonglong Li <liyonglong@...natelecom.cn> wrote:
>
> Add two new drop reasons FRAG_FAILED, FRAG_OUTPUT_FAILED.
> And use drop reasons to trace do fragment.
>
>
> Reasons show up as:
>
> perf record -e skb:kfree_skb -a; perf script
>
>   swapper 0 [005] 154.086537: skb:kfree_skb: ... location=ip6_fragment reason: PKT_TOO_BIG
>   swapper 0 [005] 154.086540: skb:kfree_skb: ... location=ip6_fragment reason: PKT_TOO_BIG
>   swapper 0 [005] 154.086544: skb:kfree_skb: ... location=ip6_fragment reason: PKT_TOO_BIG
>
> Yonglong Li (2):
>   net: ip: add drop reasons when handling ip fragments
>   net: ipv6: use drop reasons in ip6_fragment
>
>  include/net/dropreason-core.h |  6 ++++++
>  net/ipv4/ip_output.c          | 17 ++++++++++++-----
>  net/ipv6/ip6_output.c         | 16 ++++++++++++----
>  3 files changed, 30 insertions(+), 9 deletions(-)
>

Network maintainers are flooded with patches to review.

We want you to wait 24 hours before sending a new version.

Please take the time to read : Documentation/process/maintainer-netdev.rst

Resending after review
~~~~~~~~~~~~~~~~~~~~~~

Allow at least 24 hours to pass between postings. This will ensure reviewers
from all geographical locations have a chance to chime in. Do not wait
too long (weeks) between postings either as it will make it harder for reviewers
to recall all the context.

Make sure you address all the feedback in your new posting. Do not post a new
version of the code if the discussion about the previous version is still
ongoing, unless directly instructed by a reviewer.

The new version of patches should be posted as a separate thread,
not as a reply to the previous posting. Change log should include a link
to the previous posting (see :ref:`Changes requested`).