From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [FIX PATCH] spapr_rtas: Prevent QEMU crash during hotplug without a prior device_add
Date: Thu, 27 Aug 2015 10:58:57 +0530 [thread overview]
Message-ID: <20150827052857.GC11136@in.ibm.com> (raw)
In-Reply-To: <20150826141709.24880.70822@loki>
On Wed, Aug 26, 2015 at 09:17:09AM -0500, Michael Roth wrote:
> Quoting Bharata B Rao (2015-08-25 23:04:11)
> > If drmgr is used in the guest to hotplug a device before a device_add
> > has been issued via the QEMU monitor, QEMU segfaults in configure_connector
> > call. This occurs due to accessing of NULL FDT which otherwise would have
> > been created and associated with the DRC during device_add command.
> >
> > Check for NULL FDT and return failure from configure_connector call.
> >
> > Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> > Cc: Michael Roth <mdroth@linux.vnet.ibm.com>
>
> Reviewed-by: Michael Roth <mdroth@linux.vnet.ibm.com>
>
> > ---
> > Not fully sure if RTAS_OUT_HW_ERROR is the right error code here. Should
> > we be using RTAS_OUT_NOT_SUPPORTED instead ?
Based on my reading of PAPR+ 2.7, it appears that we should return -9003
error code here.
I am planning to add
#define SPAPR_DR_CC_RESPONSE_NOT_CONFIGURABLE -9003
and use it when fdt is NULL in ibm,configure-connector call. Is that fine ?
Regards,
Bharata.
next prev parent reply other threads:[~2015-08-27 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 4:04 [Qemu-devel] [FIX PATCH] spapr_rtas: Prevent QEMU crash during hotplug without a prior device_add Bharata B Rao
2015-08-26 14:17 ` Michael Roth
2015-08-27 5:28 ` Bharata B Rao [this message]
2015-08-28 20:43 ` Michael Roth
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=20150827052857.GC11136@in.ibm.com \
--to=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=mdroth@linux.vnet.ibm.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).