From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: DPDK 26.03 rc summary
Date: Fri, 13 Feb 2026 12:44:10 -0800 [thread overview]
Message-ID: <20260213124410.1ee3d328@phoenix.local> (raw)
Pointed AI at the current commits in main to see if any bugs were creeping in.
It had some good observations. I can give detail if you want.
Key takeaways:
The 26.03 cycle is overwhelmingly a hardening release — 50% of commits
carry Fixes: tags. Three major systematic efforts dominate: your format
overflow hardening series (37 patches), Bruce's variable shadowing
warning enablement (32 patches), and Marat Khalili's BPF validator/JIT
correctness fixes (9 patches).
The highest-severity finds per AGENTS.md criteria are the vhost patches
from Maxime Coquelin — particularly the descriptor chain bounds check,
which is a guest-exploitable vulnerability (no bounds check + no loop
counter on guest-controlled memory). The mmap MAP_FAILED vs NULL check
is a textbook bug that could cause memory corruption.
The NBL driver stands out as a concern — 8 correctness patches
including double-frees, NULL derefs, and 10 Coverity issues, all
shortly after its 25.11 merge. Worth extra scrutiny going forward.
New features are modest, which fits the pattern for a non-LTS release focused on quality.
reply other threads:[~2026-02-13 20:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260213124410.1ee3d328@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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