From: Kees Cook <keescook@chromium.org>
To: Nick Terrell <terrelln@meta.com>
Cc: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>
Subject: Re: Coverity: HUF_buildCTableFromTree(): Memory - corruptions
Date: Fri, 28 Oct 2022 08:55:21 -0700 [thread overview]
Message-ID: <202210280854.5DC7284@keescook> (raw)
In-Reply-To: <2B7F32C0-2068-4191-AB35-8BA6C3B94935@fb.com>
On Thu, Oct 27, 2022 at 11:07:42PM +0000, Nick Terrell wrote:
> > If these are false positives, please let us know so we can mark it as
> > such, or teach the Coverity rules to be smarter. If not, please make sure
> > fixes get into linux-next. :) For patches fixing this, please include
> > these lines (but double-check the "Fixes" first):
>
> These are all false positives.
Okay, thanks for investigating them!
--
Kees Cook
prev parent reply other threads:[~2022-10-28 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 0:05 Coverity: HUF_buildCTableFromTree(): Memory - corruptions coverity-bot
2022-10-27 13:43 ` Jann Horn
2022-10-27 18:30 ` Nick Terrell
2022-10-27 23:07 ` Nick Terrell
2022-10-28 15:55 ` 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=202210280854.5DC7284@keescook \
--to=keescook@chromium.org \
--cc=gustavo@embeddedor.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=terrelln@meta.com \
/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