public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Alexey Lapshin <alexey.lapshin@espressif.com>
To: "newlib@sourceware.org" <newlib@sourceware.org>,
	"joel.sherrill@gmail.com" <joel.sherrill@gmail.com>,
	"vinschen@redhat.com" <vinschen@redhat.com>
Subject: Re: New Defects reported by Coverity Scan for RTEMS-Newlib
Date: Tue, 11 Feb 2025 10:50:19 +0000	[thread overview]
Message-ID: <218ba4dcf69c212bd4b781aa5ed9e2155217e7c7.camel@espressif.com> (raw)
In-Reply-To: <Z6spNXNPyZj-XObC@calimero.vinschen.de>

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

Regards,
Alexey

  reply	other threads:[~2025-02-11 10:50 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 [this message]
2025-02-11 12:02       ` Corinna Vinschen
2025-02-11 15:07         ` Joel Sherrill
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=218ba4dcf69c212bd4b781aa5ed9e2155217e7c7.camel@espressif.com \
    --to=alexey.lapshin@espressif.com \
    --cc=joel.sherrill@gmail.com \
    --cc=newlib@sourceware.org \
    --cc=vinschen@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).