U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Alexander Gendin <agendin@matrox.com>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Simon Glass <sjg@chromium.org>,
	Eddie James <eajames@linux.ibm.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	Johan Jonker <jbx6244@gmail.com>,
	AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Etienne Carriere <etienne.carriere@foss.st.com>
Subject: Re: [tom.rini@gmail.com: Fwd: New Defects reported by Coverity Scan for Das U-Boot]
Date: Wed, 8 Nov 2023 09:29:22 -0500	[thread overview]
Message-ID: <20231108142922.GN6601@bill-the-cat> (raw)
In-Reply-To: <ZUr_dobret3zW48s@alg-gentoo>

[-- Attachment #1: Type: text/plain, Size: 2076 bytes --]

On Wed, Nov 08, 2023 at 03:24:38AM +0000, Alexander Gendin wrote:
> On Mon, Nov 06, 2023 at 03:27:52PM -0500, Tom Rini <trini@konsulko.com> wrote:
> 
> > Hey all,
> > 
> > Here's the latest report. I _think_ I passed the right options to
> > get_maintainer.pl such that it would only look far enough back in git to
> > find the likely authors (along with listed maintainers of the files).
> > 
> > ---------- Forwarded message ---------
> > From: <scan-admin@coverity.com>
> > Date: Mon, Nov 6, 2023 at 2:58 PM
> > Subject: New Defects reported by Coverity Scan for Das U-Boot
> > To: <tom.rini@gmail.com>
> > 
> > Hi,
> > 
> > Please find the latest report on new defect(s) introduced to Das
> > U-Boot found with Coverity Scan.
> > 
> > 13 new defect(s) introduced to Das U-Boot found with Coverity Scan.
> > 5 defect(s), reported by Coverity Scan earlier, were marked fixed in
> > the recent build analyzed by Coverity Scan.
> > 
> > New defect(s) Reported-by: Coverity Scan
> > Showing 13 of 13 defect(s)
> > 
> > <...skipped...>
> > *** CID 467404:  Control flow issues  (DEADCODE)
> > /test/cmd/mbr.c: 217 in build_mbr_parts()
> > 211                                             return 1;
> > 212                                     strcat(cur_buf, mbr_parts_p5);
> > 213                                     bytes_remaining -= cur_str_size;
> > 214
> > 215                             }
> > 216                             else if (num_parts > 5)
> > >>>     CID 467404:  Control flow issues  (DEADCODE)
> > >>>     Execution cannot reach this statement: "return 1U;".
> > 217                                     return 1;
> > 218                             }
> > 219                     }
> > 220             }
> > 221
> > 222             cur_str_size = sizeof(mbr_parts_tail);
> > <...skipped...>
> > 
> > -- 
> > Tom
> 
> Hi Tom,
> 
> Thanks for the report.
> 
> The patch to fix CID 467404 has been sent to the mailing list.

Thanks for the patch, I'll make sure to grab it before the next -rc.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-11-08 14:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 20:27 [tom.rini@gmail.com: Fwd: New Defects reported by Coverity Scan for Das U-Boot] Tom Rini
2023-11-07 11:18 ` Ilias Apalodimas
2023-11-07 23:18 ` Johan Jonker
2023-11-08 13:54   ` Tom Rini
2023-11-08  3:24 ` Alexander Gendin
2023-11-08 14:29   ` Tom Rini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-18 16:26 Tom Rini
2023-12-21 14:48 ` Shantur Rathore
2023-12-21 16:08   ` Tom Rini
2023-10-24  1:18 Tom Rini
2023-10-24 15:05 ` Sughosh Ganu
2023-10-24 18:05   ` Tom Rini
2023-07-27 17:38 Tom Rini
2023-05-29 20:04 Tom Rini
2023-03-27 19:19 Tom Rini
2023-01-31 15:02 Tom Rini
2022-12-06 14:51 Tom Rini
2022-08-24 11:40 Tom Rini
2022-09-08 18:19 ` Simon Glass
2022-08-24 11:40 Tom Rini

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=20231108142922.GN6601@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=agendin@matrox.com \
    --cc=eajames@linux.ibm.com \
    --cc=etienne.carriere@foss.st.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jbx6244@gmail.com \
    --cc=kever.yang@rock-chips.com \
    --cc=sjg@chromium.org \
    --cc=takahiro.akashi@linaro.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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