From: Dan Carpenter <dan.carpenter@linaro.org>
To: smatch@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Philip Li <philip.li@intel.com>,
lkp@intel.com
Subject: Smatch 1.74 released
Date: Thu, 22 Jan 2026 11:38:00 +0300 [thread overview]
Message-ID: <aXHh6Mu2HT8NpKjb@stanley.mountain> (raw)
A lot of people have been asking for a new release of Smatch because the
v1.73 release was from 2022 and it complicates creating distro packages.
There have been quite a few of improvements, but the main thing recently
is that I've been turning off warnings by default so that the zero day
bot can send emails without my filtering them.
I haven't been sending Spectre v1 warnings for some time. These are
places where we should add array_index_nospec(). It still an issue but
I've never felt like I've understood the issue well enough to triage
these. If anyone would like to help triage these warnigns I could
probably improve the warning a lot. (Does anyone have contacts at
Intel or AMD?)
The other warning that I disabled was about uninitialized variables. This
check is pretty good, but it requires cross function analysis and the zero
day bot doesn't do that. For example, we often have loops:
for (i = 0; i < parameter_limit; i++) {
Without cross function analysis we have to consider that parameter_limit
could be zero or even negative. The other things about uninitialized
variables is that Clang does a pretty good job warning about these.
The zero day bot has a false positive with regards to "iterator not
incremented" warnings, but I've never been able to reproduce that despite
trying really hard so I disabled that as well.
I think most people use Smatch from git but if you're using a package
then there are lots of improvements in here.
$ git log --oneline 1.73..1.74 | wc -l
874
All good things. :)
regards,
dan carpenter
reply other threads:[~2026-01-22 8:38 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=aXHh6Mu2HT8NpKjb@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=philip.li@intel.com \
--cc=smatch@vger.kernel.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