From: "Manthey, Norbert" <nmanthey@amazon.de>
To: "keescook@chromium.org" <keescook@chromium.org>
Cc: "Woodhouse, David" <dwmw@amazon.co.uk>,
"Stieger, Andreas" <astieger@amazon.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Linux kernel Coverity model file
Date: Fri, 16 Jun 2023 13:44:01 +0000 [thread overview]
Message-ID: <ccca1437bf0885924619271a3f3ddd17af018149.camel@amazon.de> (raw)
Dear Kees,
some time ago you pointed me at the github copy of the Coverity model
that is used for the Linux kernel analysis [1].
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?
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?
Best,
Norbert
[1] https://github.com/kees/coverity-linux
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
next reply other threads:[~2023-06-16 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 13:44 Manthey, Norbert [this message]
2023-06-21 18:36 ` Linux kernel Coverity model file Kees Cook
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=ccca1437bf0885924619271a3f3ddd17af018149.camel@amazon.de \
--to=nmanthey@amazon.de \
--cc=astieger@amazon.de \
--cc=dwmw@amazon.co.uk \
--cc=keescook@chromium.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.