From: Stephen Hemminger <stephen@networkplumber.org>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
netdev@vger.kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, will@willsroot.io,
jschung2@proton.me, savy@syst3mfailure.io
Subject: Re: [Bug 220774] New: netem is broken in 6.18
Date: Fri, 21 Nov 2025 16:13:22 -0800 [thread overview]
Message-ID: <20251121161322.1eb61823@phoenix.local> (raw)
In-Reply-To: <aSDdYoK7Vhw9ONzN@pop-os.localdomain>
On Fri, 21 Nov 2025 13:45:06 -0800
Cong Wang <xiyou.wangcong@gmail.com> wrote:
> On Fri, Nov 21, 2025 at 07:52:37AM -0500, Jamal Hadi Salim wrote:
>
> > jschung2@proton.me: Can you please provide more details about what you
> > are trying to do so we can see if a different approach can be
> > prescribed?
> >
>
> An alternative approach is to use eBPF qdisc to replace netem, but:
> 1) I am not sure if we could duplicate and re-inject a packet in eBPF Qdisc
> 2) I doubt everyone wants to write eBPF code when they already have a
> working cmdline.
>
> BTW, Jamal, if your plan is to solve them one by one, even if it could work,
> it wouldn't scale. There are still many users don't get hit by this
> regression yet (not until hitting LTS or major distro).
>
> Regards,
> Cong
The bug still needs to be fixed.
eBPF would still have the same kind of issues.
next prev parent reply other threads:[~2025-11-22 0:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 20:38 Fw: [Bug 220774] New: netem is broken in 6.18 Stephen Hemminger
2025-11-21 4:29 ` Cong Wang
2025-11-21 12:52 ` Jamal Hadi Salim
2025-11-21 21:45 ` Cong Wang
2025-11-22 0:13 ` Stephen Hemminger [this message]
2025-11-22 1:55 ` Jakub Kicinski
2025-11-22 17:16 ` Jamal Hadi Salim
2025-11-22 18:14 ` Cong Wang
2025-11-25 3:16 ` Jakub Kicinski
2025-11-25 4:20 ` William Liu
2025-11-26 4:48 ` Cong Wang
2025-11-22 6:56 ` Fw: " 정지수
2025-11-22 17:24 ` Jamal Hadi Salim
2025-11-22 18:22 ` Cong Wang
2025-11-27 6:08 ` 정지수
2025-11-27 15:11 ` Jamal Hadi Salim
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=20251121161322.1eb61823@phoenix.local \
--to=stephen@networkplumber.org \
--cc=jhs@mojatatu.com \
--cc=jschung2@proton.me \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=savy@syst3mfailure.io \
--cc=will@willsroot.io \
--cc=xiyou.wangcong@gmail.com \
/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.