From: Kees Cook <keescook@chromium.org>
To: "Manthey, Norbert" <nmanthey@amazon.de>
Cc: "Woodhouse, David" <dwmw@amazon.co.uk>,
"Stieger, Andreas" <astieger@amazon.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-hardening@vger.kernel.org
Subject: Re: Linux kernel Coverity model file
Date: Wed, 21 Jun 2023 11:36:06 -0700 [thread overview]
Message-ID: <202306211134.C301FEB6@keescook> (raw)
In-Reply-To: <ccca1437bf0885924619271a3f3ddd17af018149.camel@amazon.de>
On Fri, Jun 16, 2023 at 01:44:01PM +0000, Manthey, Norbert wrote:
> some time ago you pointed me at the github copy of the Coverity model
> that is used for the Linux kernel analysis [1].
Hi!
> I investigated the effect of using this model, and compared defects
> reported with and without the model. Before I deep dive into
> modifications, I wanted to understand whether there is a more recent
> version (the current one is about 4 years old). I currently have no
> access to the public linux dashboard to directly check the effect
> there.
>
> In case there is a more recent model file, can you please update the
> github repository?
This model file is current -- we haven't changed it in quite some time.
> In case I find additions, is the following a good procedure to share
> model updates? I would run an analysis on a defined Linux commit with
> the current model and the proposed additions, and would report the
> effect on the reported defects. Is there anything else I am missing?
Yes please! Either send a patch to the linux-hardening@vger.kernel.org
mailing list or send a PR to the github repo.
-Kees
> [1] https://github.com/kees/coverity-linux
--
Kees Cook
prev parent reply other threads:[~2023-06-21 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 13:44 Linux kernel Coverity model file Manthey, Norbert
2023-06-21 18:36 ` Kees Cook [this message]
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=202306211134.C301FEB6@keescook \
--to=keescook@chromium.org \
--cc=astieger@amazon.de \
--cc=dwmw@amazon.co.uk \
--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