[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aSaGsdNk/h0TuB+b@pop-os.localdomain>
Date: Tue, 25 Nov 2025 20:48:49 -0800
From: Cong Wang <xiyou.wangcong@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Stephen Hemminger <stephen@...workplumber.org>,
Jamal Hadi Salim <jhs@...atatu.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, will@...lsroot.io, jschung2@...ton.me,
savy@...t3mfailure.io
Subject: Re: [Bug 220774] New: netem is broken in 6.18
On Mon, Nov 24, 2025 at 07:16:25PM -0800, Jakub Kicinski wrote:
> On Sat, 22 Nov 2025 10:14:50 -0800 Cong Wang wrote:
> > > I guess we forgot about mq.. IIRC mq doesn't come into play in
> > > duplication, we should be able to just adjust the check to allow
> >
> > This is not true, I warned you and Jamal with precisely the mq+netem
> > combination before applying the patch, both of you chose to ignore.
>
> I'm curious why we did.. Link?
https://lore.kernel.org/all/aG10rqwjX6elG1Gx@pop-os.localdomain/#t
Jamal just denied the use case and let users complain.
This strategy does not work, since majority users would need to wait
until LTS gets hit by this regression. (IMHO, it is also unethical to
knowingly break valid use cases, regardless of purpose.)
Regards,
Cong Wang
Powered by blists - more mailing lists