From: Kees Cook <kees@kernel.org>
To: linux-hardening@vger.kernel.org
Subject: Coverity scanning offline
Date: Wed, 14 Jan 2026 10:56:07 -0800 [thread overview]
Message-ID: <202601141054.4A30A22@keescook> (raw)
Hi,
I mentioned this on Fedi[1], but I should repeat it here: Coverity
scanning is offline until it supports[2] -fms-extensions for transparent
structs, which were enabled globally in Linux after v6.18.
-Kees
[1] https://hachyderm.io/@kees/115894901529239937
[2] https://community.blackduck.com/s/question/0D5Ul00000cztsCKAQ/linux-scanning-is-broken-coverity-needs-to-support-fmsextensions-option
--
Kees Cook
reply other threads:[~2026-01-14 18:56 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=202601141054.4A30A22@keescook \
--to=kees@kernel.org \
--cc=linux-hardening@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