From: Greg KH <gregkh@linuxfoundation.org>
To: "Manthey, Norbert" <nmanthey@amazon.de>
Cc: "keescook@chromium.org" <keescook@chromium.org>,
"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 18:15:05 +0200 [thread overview]
Message-ID: <2024051625-dowry-pacifism-b0b9@gregkh> (raw)
In-Reply-To: <77f6e6fc46232db82a3c63e93877c9534334e407.camel@amazon.de>
On Thu, May 16, 2024 at 03:28:16PM +0000, Manthey, Norbert wrote:
> Dear Kees, all,
>
> 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.
>
> 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.
>
> 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?
New defects yes, I would like to know that, as long as they are also
fixed already in mainline, right?
Just send us reports of that, no need to get the covertity site involved
there, I'll be glad to take them.
thanks,
greg k-h
next prev parent reply other threads:[~2024-05-16 16:15 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 [this message]
2024-05-16 19:20 ` Kees Cook
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=2024051625-dowry-pacifism-b0b9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=astieger@amazon.de \
--cc=dwmw@amazon.co.uk \
--cc=hagarhem@amazon.de \
--cc=keescook@chromium.org \
--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).