From: Shivaprasad G Bhat <sbhat@linux.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>,
David Gibson <david@gibson.dropbear.id.au>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"Alexey Kardashevskiy" <aik@ozlabs.ru>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Greg Kurz" <groug@kaod.org>, qemu-ppc <qemu-ppc@nongnu.org>,
"Cédric Le Goater" <clg@kaod.org>,
"Bharata B Rao" <bharata@linux.ibm.com>
Subject: Re: [PULL 07/20] spapr: Add NVDIMM device support
Date: Wed, 26 Feb 2020 17:43:34 +0530 [thread overview]
Message-ID: <c26ee672-061a-ea06-9b81-f55c8fed67f7@linux.ibm.com> (raw)
In-Reply-To: <CAFEAcA8GZ-YkfQJ9TMAOoLe++WF9+YZT1rw_F8xLPxY+ciBhMg@mail.gmail.com>
On 02/25/2020 03:30 PM, Peter Maydell wrote:
> On Fri, 21 Feb 2020 at 03:37, David Gibson <david@gibson.dropbear.id.au> wrote:
>> From: Shivaprasad G Bhat <sbhat@linux.ibm.com>
>>
>> Add support for NVDIMM devices for sPAPR. Piggyback on existing nvdimm
>> device interface in QEMU to support virtual NVDIMM devices for Power.
>> + }
>> +
>> + uuidstr = object_property_get_str(OBJECT(nvdimm), NVDIMM_UUID_PROP, NULL);
>> + qemu_uuid_parse(uuidstr, &uuid);
>> + g_free(uuidstr);
>> +
>> + if (qemu_uuid_is_null(&uuid)) {
>> + error_setg(errp, "NVDIMM device requires the uuid to be set");
>> + return;
>> + }
>> +}
> Hi -- Coverity thinks (CID 1419883) that it's suspicious that
> this code doesn't check the return value of qemu_uuid_parse(),
> because we check it everywhere else that we call that function
> (it can return a failure code if the UUID doesn't validly parse).
Hi Peter,
The nvdimm_set_uuid() already verifies if the uuid is valid or not. So,
its safe
if we dont check here again.
I just posted a patch adding an assert here.
Thanks and Regards,
Shivaprasad
next prev parent reply other threads:[~2020-02-26 12:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 3:36 [PULL 00/20] ppc-for-5.0 queue 20200221 David Gibson
2020-02-21 3:36 ` [PULL 01/20] spapr/rtas: Print message from "ibm,os-term" David Gibson
2020-02-21 3:36 ` [PULL 02/20] qtest: Fix rtas dependencies David Gibson
2020-02-21 3:36 ` [PULL 03/20] ppc/pnv: Fix PCI_EXPRESS dependency David Gibson
2020-02-21 3:36 ` [PULL 04/20] ppc: function to setup latest class options David Gibson
2020-02-21 3:36 ` [PULL 05/20] mem: move nvdimm_device_list to utilities David Gibson
2020-04-03 12:34 ` Peter Maydell
2020-02-21 3:36 ` [PULL 06/20] nvdimm: add uuid property to nvdimm David Gibson
2020-02-21 3:36 ` [PULL 07/20] spapr: Add NVDIMM device support David Gibson
2020-02-25 10:00 ` Peter Maydell
2020-02-26 12:13 ` Shivaprasad G Bhat [this message]
2020-02-21 3:36 ` [PULL 08/20] spapr: Add Hcalls to support PAPR NVDIMM device David Gibson
2020-02-21 3:36 ` [PULL 09/20] target/ppc/cpu.h: Remove duplicate includes David Gibson
2020-02-21 3:36 ` [PULL 10/20] pnv/phb3: Convert 1u to 1ull David Gibson
2020-02-21 3:36 ` [PULL 11/20] pnv/phb4: Fix error path in pnv_pec_realize() David Gibson
2020-02-21 3:36 ` [PULL 12/20] pnv/phb3: Add missing break statement David Gibson
2020-02-21 3:36 ` [PULL 13/20] spapr: Allow changing offset for -kernel image David Gibson
2020-02-21 3:36 ` [PULL 14/20] target/ppc: Fix typo in comments David Gibson
2020-02-21 3:36 ` [PULL 15/20] target/ppc/cpu.h: Move fpu related members closer in cpu env David Gibson
2020-02-21 3:36 ` [PULL 16/20] target/ppc/cpu.h: Clean up comments in the struct CPUPPCState definition David Gibson
2020-02-21 3:36 ` [PULL 17/20] ppc: free 'fdt' after reset the machine David Gibson
2020-02-21 3:36 ` [PULL 18/20] spapr: Don't use spapr_drc_needed() in CAS code David Gibson
2020-02-21 3:36 ` [PULL 19/20] spapr: Fix handling of unplugged devices during CAS and migration David Gibson
2020-02-21 3:36 ` [PULL 20/20] hw/ppc/virtex_ml507:fix leak of fdevice tree blob David Gibson
2020-02-21 15:18 ` [PULL 00/20] ppc-for-5.0 queue 20200221 Peter Maydell
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=c26ee672-061a-ea06-9b81-f55c8fed67f7@linux.ibm.com \
--to=sbhat@linux.ibm.com \
--cc=aik@ozlabs.ru \
--cc=bharata@linux.ibm.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--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).