From: Kees Cook <keescook@chromium.org>
To: Amit Kucheria <amit.kucheria@linaro.org>
Cc: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Colin King <colin.king@canonical.com>,
AngeloGioacchino Del Regno <kholk11@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Linux-Next <linux-next@vger.kernel.org>
Subject: Re: Coverity: calibrate_8976(): Memory - illegal accesses
Date: Tue, 29 Oct 2019 09:17:45 -0700 [thread overview]
Message-ID: <201910290916.087AA12F@keescook> (raw)
In-Reply-To: <CAP245DWT+5xhqHY2w-WPH+-Q0Tujw57UaezqqrT3JRwSVq5iSQ@mail.gmail.com>
On Tue, Oct 29, 2019 at 09:37:57PM +0530, Amit Kucheria wrote:
> On Tue, Oct 29, 2019 at 9:30 PM Kees Cook <keescook@chromium.org> wrote:
> >
> > On Mon, Oct 28, 2019 at 5:08 PM Gustavo A. R. Silva
> > <gustavo@embeddedor.com> wrote:
> > >
> > > Hi,
> > >
> > > This one has been addressed already:
> > >
> > > https://lore.kernel.org/lkml/CAK7fi1a8CiX=HVqhZSmQJdcjF1X_kdHFDwJhEpYJUcdPTcbMQA@mail.gmail.com/
> > >
> >
> > Ah-ha, excellent. Colin, do you want me to CC you on these automatic
> > reports too?
> >
>
> Hi Kees,
>
> Is coverity being run just on linux-next or on mainline too? I've
> noticed it found at least one error that has existed for a long-time
> only when that code was moved around.
There is another public Coverity scan that runs the -rcX releases. Dave
Jones tends to operate that one, and I haven't attached any tooling to
that one. I wanted to see how noisy running against linux-next was
first...
--
Kees Cook
prev parent reply other threads:[~2019-10-29 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 23:03 Coverity: calibrate_8976(): Memory - illegal accesses coverity-bot
2019-10-28 23:44 ` Gustavo A. R. Silva
2019-10-29 15:59 ` Kees Cook
2019-10-29 16:07 ` Amit Kucheria
2019-10-29 16:17 ` 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=201910290916.087AA12F@keescook \
--to=keescook@chromium.org \
--cc=amit.kucheria@linaro.org \
--cc=colin.king@canonical.com \
--cc=daniel.lezcano@linaro.org \
--cc=gustavo@embeddedor.com \
--cc=kholk11@gmail.com \
--cc=linux-next@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.