From: Joel Sherrill <joel.sherrill@gmail.com>
To: newlib@sourceware.org,
Alexey Lapshin <alexey.lapshin@espressif.com>,
"joel.sherrill@gmail.com" <joel.sherrill@gmail.com>
Subject: Re: New Defects reported by Coverity Scan for RTEMS-Newlib
Date: Tue, 11 Feb 2025 09:07:43 -0600 [thread overview]
Message-ID: <CAF9ehCXEYKkK_fvb6O5aHBe8U2NQykq7AY4K6Dgu_L9N27bBTQ@mail.gmail.com> (raw)
In-Reply-To: <Z6s8ZxEK_oiTLdZK@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
Confirming I should mark then as false positives.
Thanks.
On Tue, Feb 11, 2025 at 6:02 AM Corinna Vinschen <vinschen@redhat.com>
wrote:
> On Feb 11 10:50, Alexey Lapshin wrote:
> > Hi, interesting finding,
> >
> > Are not all these found "underflows" issues false-positive?
> > Because all of them are under `while(!TOO_SMALL_LITTLE_BLOCK(len))` block
> > which guarantees no underflow of "len" variable
>
> Yeah, looks like false positives to me, too.
>
>
> Corinna
>
>
next prev parent reply other threads:[~2025-02-11 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <67aa7d4565885_1e98fe2ac1a16659a8550b1@prd-scan-dashboard-0.mail>
2025-02-10 22:56 ` Fwd: " Joel Sherrill
2025-02-11 10:40 ` Corinna Vinschen
2025-02-11 10:50 ` Alexey Lapshin
2025-02-11 12:02 ` Corinna Vinschen
2025-02-11 15:07 ` Joel Sherrill [this message]
2025-02-11 21:24 ` Brian Inglis
[not found] <630d44245d07b_448622ac7e91099ac81e@prd-scan-dashboard-0.mail>
2022-08-29 23:09 ` Fwd: " Joel Sherrill
2022-08-30 19:03 ` Jeff Johnston
2022-08-30 19:03 ` Jeff Johnston
2022-08-31 19:16 ` Jeff Johnston
2022-08-31 19:16 ` Jeff Johnston
2022-08-31 19:58 ` Joel Sherrill
2022-08-31 19:58 ` Joel Sherrill
[not found] <621dbc6e5b779_bb4ce2b0cf36619a0847b1@prd-scan-dashboard-0.mail>
2022-03-01 12:59 ` Fwd: " Joel Sherrill
[not found] ` <BN2P110MB1544826C2DADD0A490C6E5E49A029@BN2P110MB1544.NAMP110.PROD.OUTLOOK.COM>
2022-03-01 19:30 ` C Howland
2022-03-01 20:43 ` Joel Sherrill
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=CAF9ehCXEYKkK_fvb6O5aHBe8U2NQykq7AY4K6Dgu_L9N27bBTQ@mail.gmail.com \
--to=joel.sherrill@gmail.com \
--cc=alexey.lapshin@espressif.com \
--cc=newlib@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).