Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: zyc zyc <zyc199902@zohomail.cn>
Cc: stable <stable@vger.kernel.org>
Subject: Re: 回复:6.12.50 regression: netem: cannot mix duplicating netems with other netems in tree.
Date: Tue, 2 Dec 2025 12:30:09 +0100	[thread overview]
Message-ID: <2025120248-operation-explain-1991@gregkh> (raw)
In-Reply-To: <19adda5a1e2.12410b78222774.9191120410578703463@zohomail.cn>

On Tue, Dec 02, 2025 at 06:39:00PM +0800, zyc zyc wrote:
> Hello,
> 
> Resend my last email without HTML.
> 
> ---- zyc zyc <zyc199902@zohomail.cn> 在 Sat, 2025-11-29 18:57:01 写到:---
> 
>  > Hello, maintainer
>  > 
>  > I would like to report what appears to be a regression in 6.12.50 kernel release related to netem.
>  > It rejects our configuration with the message:
>  > Error: netem: cannot mix duplicating netems with other netems in tree.
>  > 
>  > This breaks setups that previously worked correctly for many years.
>  > 
>  > 
>  > Our team uses multiple netem qdiscs in the same HTB branch, arranged in a parallel fashion using a prio fan-out. Each branch of the prio qdisc has its own distinct netem instance with different duplication characteristics.
>  > 
>  > This is used to emulate our production conditions where a single logical path fans out into two downstream segments, for example:
>  > 
>  > two ECMP next hops with different misbehaviour characteristics, or
>  > 
>  > 
>  > an HA firewall cluster where only one node is replaying frames, or
>  > 
>  > 
>  > two LAG / ToR paths where one path intermittently duplicates packets.
>  > 
>  > 
>  > In our environments, only a subset of flows are affected, and different downstream devices may cause different styles of duplication.
>  > This regression breaks existing automated tests, training environments, and network simulation pipelines.
>  > 
>  > I would be happy to provide our reproducer if needed.
>  > 
>  > Thank you for your time and for maintaining Linux kernel.

Can you use 'git bisect' to find the offending commit?

thanks,

greg k-h

  reply	other threads:[~2025-12-02 11:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19ace674022.114eb26e714992.3171091003233609170@zohomail.cn>
2025-12-02 10:39 ` 回复:6.12.50 regression: netem: cannot mix duplicating netems with other netems in tree zyc zyc
2025-12-02 11:30   ` Greg KH [this message]
2025-12-03 11:05     ` zyc zyc
2025-12-03 11:30       ` Greg KH
2025-12-05 10:31         ` zyc zyc
2025-12-08  9:59           ` zyc zyc
2025-12-10  3:31             ` William Liu
2025-12-17  9:04               ` zyc zyc

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=2025120248-operation-explain-1991@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=zyc199902@zohomail.cn \
    /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