From: patchwork-bot+netdevbpf@kernel.org
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, jiri@resnulli.us, jhs@mojatatu.com,
horms@kernel.org
Subject: Re: [PATCH v8 net 0/6] netem: bug fixes
Date: Tue, 28 Apr 2026 00:40:14 +0000 [thread overview]
Message-ID: <177733681455.174583.13249817958251162504.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260418032027.900913-1-stephen@networkplumber.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 17 Apr 2026 20:19:38 -0700 you wrote:
> These bugs were found when doing AI-assisted review of sch_netem.c
> during investigation of the packet duplication recursion problem
> addressed in Jamal's series.
>
> The fixes cover:
>
> - probability gaps in the 4-state Markov loss model
> - queue limit not accounting for reordered packets
> - PRNG reseeded on every tc change, breaking reproducibility
> - slot configuration not validated (inverted ranges, negative
> delays, negative limits)
> - slot delay arithmetic overflow for ranges above ~2.1 seconds
> - negative latency and jitter wrapping to huge time_to_send
> values via u64 arithmetic
>
> [...]
Here is the summary with links:
- [net,v8,1/6] net/sched: netem: fix probability gaps in 4-state loss model
https://git.kernel.org/netdev/net/c/732b463449fd
- [net,v8,2/6] net/sched: netem: fix queue limit check to include reordered packets
https://git.kernel.org/netdev/net/c/4185701fcce6
- [net,v8,3/6] net/sched: netem: only reseed PRNG when seed is explicitly provided
https://git.kernel.org/netdev/net/c/986afaf80994
- [net,v8,4/6] net/sched: netem: validate slot configuration
https://git.kernel.org/netdev/net/c/01801c359a74
- [net,v8,5/6] net/sched: netem: fix slot delay calculation overflow
https://git.kernel.org/netdev/net/c/51e94e1e2fef
- [net,v8,6/6] net/sched: netem: check for negative latency and jitter
https://git.kernel.org/netdev/net/c/90be9fedb218
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-28 0:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 3:19 [PATCH v8 net 0/6] netem: bug fixes Stephen Hemminger
2026-04-18 3:19 ` [PATCH net v8 1/6] net/sched: netem: fix probability gaps in 4-state loss model Stephen Hemminger
2026-04-18 3:19 ` [PATCH net v8 2/6] net/sched: netem: fix queue limit check to include reordered packets Stephen Hemminger
2026-04-21 13:15 ` Simon Horman
2026-04-18 3:19 ` [PATCH net v8 3/6] net/sched: netem: only reseed PRNG when seed is explicitly provided Stephen Hemminger
2026-04-18 3:19 ` [PATCH net v8 4/6] net/sched: netem: validate slot configuration Stephen Hemminger
2026-04-21 13:10 ` Simon Horman
2026-04-23 7:50 ` Paolo Abeni
2026-04-23 21:12 ` Jamal Hadi Salim
2026-04-24 15:07 ` Stephen Hemminger
2026-04-24 20:17 ` Jamal Hadi Salim
2026-04-24 23:06 ` Stephen Hemminger
2026-04-18 3:19 ` [PATCH net v8 5/6] net/sched: netem: fix slot delay calculation overflow Stephen Hemminger
2026-04-18 3:19 ` [PATCH net v8 6/6] net/sched: netem: check for negative latency and jitter Stephen Hemminger
2026-04-21 13:16 ` Simon Horman
2026-04-28 0:40 ` patchwork-bot+netdevbpf [this message]
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=177733681455.174583.13249817958251162504.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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