From: Kees Cook <keescook@chromium.org>
To: "Manthey, Norbert" <nmanthey@amazon.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
"Stieger, Andreas" <astieger@amazon.de>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>,
"Hemdan, Hagar Gamal Halim" <hagarhem@amazon.de>
Subject: Re: Extending Linux' Coverity model and also cover aarch64
Date: Thu, 16 May 2024 12:20:19 -0700 [thread overview]
Message-ID: <202405161217.4984DE258@keescook> (raw)
In-Reply-To: <77f6e6fc46232db82a3c63e93877c9534334e407.camel@amazon.de>
On Thu, May 16, 2024 at 03:28:16PM +0000, Manthey, Norbert wrote:
> we published an extension for the Coverity model that is used by the
> CoverityScan setup for the Linux kernel [1]. We have been using this
> extension to analyze the 6.1 kernel branch, and reported some fixes to
> the upstream code base that are based on this model [2]. Feel free to
> merge the pull request, and update the model in the CoverityScan setup.
> We do not have access to that project to perform these updates
> ourselves.
Thanks for this! I'll get it loaded into the Linux-Next scanner.
> To increase the analysis coverage to aarch64, we analyzed a x86 and a
> aarch64 configuration. The increased coverage is achieved by using re-
> configuration and cross-compilation during the analysis build. If you
> are interested in this setup we can share the Dockerfile and script we
> used for this process.
We've only got access to the free Coverity scanner, but it would be nice
to see if there was anything specific to arm64.
> To prevent regressions in backports to LTS kernels, we wondered whether
> the community is interested in setting up CoverityScan projects for
> older kernel releases. Would such an extension be useful to show new
> defects in addition to the current release testing?
The only one we (lightly) manage right now is the linux-next scanner. If
other folks want to host scanners for -stable kernels, that would be
interesting, yes.
-Kees
--
Kees Cook
next prev parent reply other threads:[~2024-05-16 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 15:28 Extending Linux' Coverity model and also cover aarch64 Manthey, Norbert
2024-05-16 16:15 ` Greg KH
2024-05-16 19:20 ` Kees Cook [this message]
2024-05-17 6:19 ` Manthey, Norbert
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=202405161217.4984DE258@keescook \
--to=keescook@chromium.org \
--cc=astieger@amazon.de \
--cc=dwmw@amazon.co.uk \
--cc=hagarhem@amazon.de \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nmanthey@amazon.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).