netdev - Re: [PATCH net v5 1/2] net/sched: Restrict conditions for adding duplicating netems to qdisc tree

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] [day] [month] [year] [list]

Message-ID: <20250714075812.3e9adfed@kernel.org>
Date: Mon, 14 Jul 2025 07:58:12 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: William Liu <will@...lsroot.io>
Cc: netdev@...r.kernel.org, jhs@...atatu.com, xiyou.wangcong@...il.com,
 victor@...atatu.com, pctammela@...atatu.com, pabeni@...hat.com,
 stephen@...workplumber.org, dcaratti@...hat.com, savy@...t3mfailure.io,
 jiri@...nulli.us, davem@...emloft.net, edumazet@...gle.com,
 horms@...nel.org
Subject: Re: [PATCH net v5 1/2] net/sched: Restrict conditions for adding
 duplicating netems to qdisc tree

On Sat, 12 Jul 2025 16:51:39 +0000 William Liu wrote:
> > We already had one regression scare this week, so given that Cong
> > is not relenting I'll do the unusual thing of parking this fix in
> > net-next. It will reach Linus during the merge window, hopefully
> > the <2 week delay is not a big deal given how long we've taken already.  
> 
> If this is going to net-next, will this still be a candidate for
> backporting like other recent net/sched bug-fixes? Or will this only
> be considered fixed starting 6.17 onwards?

It will be a candidate for backporting once it reaches Linus.
The only difference is timing.