From: Corinna Vinschen <vinschen@redhat.com>
To: Joel Sherrill <joel@rtems.org>
Cc: Newlib <newlib@sourceware.org>
Subject: Re: Coverity Scan: Analysis completed for RTEMS-Newlib
Date: Mon, 13 Nov 2023 17:21:34 +0100 [thread overview]
Message-ID: <ZVJNDuFcDHJffog0@calimero.vinschen.de> (raw)
In-Reply-To: <CAF9ehCX=Fpf5dJirhoc+O-5ijAPUYHkYbqFJNjvaM=-69oLq8A@mail.gmail.com>
On Nov 13 08:23, Joel Sherrill wrote:
> On Mon, Nov 13, 2023, 7:19 AM Corinna Vinschen <vinschen@redhat.com> wrote:
>
> > On Nov 10 11:44, Joel Sherrill wrote:
> > > On Fri, Nov 10, 2023 at 9:32 AM Corinna Vinschen <vinschen@redhat.com>
> > > wrote:
> > >
> > > > On Nov 10 08:50, Joel Sherrill wrote:
> > > > > Hmmmm.. an email just before the one I forwarded shows 6 new defects
> > were
> > > > > added in the last commits. They appear to be the same issue I just
> > > > > forwarded but in different scanf variants.
> > > > >
> > > > > CID 423229 (#1 of 1): Uninitialized scalar variable (UNINIT)2.
> > > > > uninit_use_in_call: Using uninitialized value f._flags2 when calling
> > > > > __ssvfiscanf_r. [show details
> > > > > <
> > > >
> > https://scan3.scan.coverity.com/eventId=13202494-1&modelId=13202494-0&fileInstanceId=104130545&filePath=%2Fhome%2Fjoel%2Frtems-cron-coverity%2Fsourceware-mirror-newlib-cygwin%2Fnewlib%2Flibc%2Fstdio%2Fvfscanf.c&fileStart=400&fileEnd=1980
> > > > >
> > > > > ]
> > > >
> > > > Looks like a false positive.
> > > >
> > > > The ORIENT macro will set or reset the value of the _flags2 __SWID bit
> > > > if the _flags __SORD bit isn't set. It never is set at the start, so
> > > > the _flags2 __SWID bit is always set. And only then, the ORIENT macro
> > > > will check the value.
> > > >
> > >
> > > Thanks. I will mark them as false positive.
> > >
> > > What about the issue in the printf variants? Looks like similar code. Are
> > > they
> > > also false positives? This is from asiprintf.c
> > >
> > > 37 f._flags = __SWR | __SSTR | __SMBF;
> > >
> > > 1. assign_zero: Assigning: f._p = NULL.
> > > 38 f._bf._base = f._p = NULL;
> > > 39 f._bf._size = f._w = 0;
> > > 40 f._file = -1; /* No file. */
> > > 41 va_start (ap, fmt);
> > >
> > > CID 387497 (#2 of 2): Explicit null dereferenced (FORWARD_NULL)2.
> > > var_deref_model: Passing &f to _svfiprintf_r, which dereferences null
> > f._p.
> > > [show details
> > > <
> > https://scan3.scan.coverity.com/eventId=13202490-1&modelId=13202490-0&fileInstanceId=104130544&filePath=%2Fhome%2Fjoel%2Frtems-cron-coverity%2Fsourceware-mirror-newlib-cygwin%2Fnewlib%2Flibc%2Fstdio%2Fvfprintf.c&fileStart=650&fileEnd=1786
> > >
> > > ]
> > > 42 ret = _svfiprintf_r (ptr, &f, fmt, ap);
> >
> > Did you try to debug it?
> >
>
> No. It just looked similar and was introduced earlier this year.
Then please, do.
Thanks,
Corinna
prev parent reply other threads:[~2023-11-13 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <654dcb688da84_69bd52d4ed1e699a037313@prd-scan-dashboard-0.mail>
2023-11-10 14:50 ` Fwd: " Joel Sherrill
2023-11-10 15:31 ` Corinna Vinschen
2023-11-10 15:55 ` Takashi Yano
2023-11-10 15:59 ` Takashi Yano
2023-11-15 13:50 ` Corinna Vinschen
2023-11-10 17:44 ` Joel Sherrill
2023-11-13 13:19 ` Corinna Vinschen
2023-11-13 14:23 ` Joel Sherrill
2023-11-13 16:21 ` Corinna Vinschen [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=ZVJNDuFcDHJffog0@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=joel@rtems.org \
--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).