qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: qemu-ppc@nongnu.org, "Cédric Le Goater" <clg@kaod.org>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] ppc/pnv: check return value of blk_pwrite()
Date: Wed, 8 Jan 2020 11:56:50 +1100	[thread overview]
Message-ID: <20200108005650.GE2137@umbus.fritz.box> (raw)
In-Reply-To: <49613a4e-aec8-8ae3-4443-ede9ed1fd39f@redhat.com>

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

On Tue, Jan 07, 2020 at 07:22:18PM +0100, Philippe Mathieu-Daudé wrote:
> On 1/7/20 6:18 PM, Cédric Le Goater wrote:
> > When updating the PNOR file contents, we should check for a possible
> > failure of blk_pwrite().
> > 
> > Fixes Coverity issue CID 1412228.
> > 
> > Signed-off-by: Cédric Le Goater <clg@kaod.org>
> > ---
> >   hw/ppc/pnv_pnor.c | 8 ++++++--
> >   1 file changed, 6 insertions(+), 2 deletions(-)
> > 
> > diff --git a/hw/ppc/pnv_pnor.c b/hw/ppc/pnv_pnor.c
> > index bfb1e92b0392..0e86ae2feae6 100644
> > --- a/hw/ppc/pnv_pnor.c
> > +++ b/hw/ppc/pnv_pnor.c
> > @@ -33,6 +33,7 @@ static uint64_t pnv_pnor_read(void *opaque, hwaddr addr, unsigned size)
> >   static void pnv_pnor_update(PnvPnor *s, int offset, int size)
> >   {
> >       int offset_end;
> > +    int ret;
> >       if (s->blk) {
> >           return;
> > @@ -42,8 +43,11 @@ static void pnv_pnor_update(PnvPnor *s, int offset, int size)
> >       offset = QEMU_ALIGN_DOWN(offset, BDRV_SECTOR_SIZE);
> >       offset_end = QEMU_ALIGN_UP(offset_end, BDRV_SECTOR_SIZE);
> > -    blk_pwrite(s->blk, offset, s->storage + offset,
> > -               offset_end - offset, 0);
> > +    ret = blk_pwrite(s->blk, offset, s->storage + offset,
> > +                     offset_end - offset, 0);
> > +    if (ret < 0) {
> > +        error_report("Could not update PNOR: %s", strerror(-ret));
> 
> Can you report the failed offset too please?

Since this fixes a coverity warning, I'm applying now, and extending
the error message can be a followup.

> 
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> 
> > +    }
> >   }
> >   static void pnv_pnor_write(void *opaque, hwaddr addr, uint64_t data,
> > 
> 

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

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

  reply	other threads:[~2020-01-08  1:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 17:18 [PATCH 0/2] ppc/pnv: PNOR fixes Cédric Le Goater
2020-01-07 17:18 ` [PATCH 1/2] ppc/pnv: check return value of blk_pwrite() Cédric Le Goater
2020-01-07 17:40   ` Greg Kurz
2020-01-07 18:22   ` Philippe Mathieu-Daudé
2020-01-08  0:56     ` David Gibson [this message]
2020-01-07 17:18 ` [PATCH 2/2] ppc/pnv: fix check on return value of blk_getlength() Cédric Le Goater
2020-01-07 17:42   ` Greg Kurz
2020-01-07 18:23   ` Philippe Mathieu-Daudé
2020-01-08  1:01   ` David Gibson

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=20200108005650.GE2137@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=clg@kaod.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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 NNTP newsgroup(s).