From: Kroah-Hartman <greg@kroah.com>
To: Norbert Manthey <nmanthey@amazon.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
"foersleo@amazon.de" <foersleo@amazon.de>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
"Gustavo A. R. Silva" <garsilva@embeddedor.com>,
Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Coverity Scan model file, license, public access
Date: Tue, 6 Jul 2021 20:41:54 +0200 [thread overview]
Message-ID: <YOSj8kjDtjmUtcVP@kroah.com> (raw)
In-Reply-To: <6f1cb856-fc72-cfd1-9bdd-b4dbf58c558c@amazon.de>
On Tue, Jul 06, 2021 at 08:34:16PM +0200, Norbert Manthey wrote:
> With respect to sharing the results: we are allowed to upstream fixes
> that we find with the tool. We contributed in that way already, e.g. [2].
Yes, that is how many companies do this and have for a long time
(Canonical does this a lot). But that puts all the work on you, and you
can not share the results of the tool with anyone, so you are forced to
do the work to fix problems the tool reports, which feels really wrong
when you are dealing with a scan of a public source tree...
thanks,
greg k-h
next prev parent reply other threads:[~2021-07-06 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 7:45 Coverity Scan model file, license, public access Norbert Manthey
2021-07-06 16:54 ` Kroah-Hartman
[not found] ` <6f1cb856-fc72-cfd1-9bdd-b4dbf58c558c@amazon.de>
2021-07-06 18:41 ` Kroah-Hartman [this message]
[not found] ` <b5f5c38c-5691-816d-f14c-8a82be7d9456@amazon.de>
2021-07-07 5:16 ` Kroah-Hartman
2021-07-15 13:12 ` Norbert Manthey
2021-07-15 18:25 ` Kees Cook
2021-07-16 10:26 ` Norbert Manthey
2021-12-17 19:32 ` Muhammad Usama Anjum
2021-12-17 20:03 ` Gustavo A. R. Silva
2021-12-17 23:31 ` Kroah-Hartman
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=YOSj8kjDtjmUtcVP@kroah.com \
--to=greg@kroah.com \
--cc=dwmw@amazon.co.uk \
--cc=foersleo@amazon.de \
--cc=garsilva@embeddedor.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nmanthey@amazon.de \
--cc=tglx@linutronix.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