From: Thomas Huth <thuth@redhat.com>
To: Wei Yang <richardw.yang@linux.intel.com>,
Wei Yang <richard.weiyang@gmail.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-4.0] hw/i386/pc: Fix crash when hot-plugging nvdimm on older machine types
Date: Thu, 11 Apr 2019 06:50:38 +0200 [thread overview]
Message-ID: <8c0c99e1-3f9c-f852-aa0d-7a4a31856392@redhat.com> (raw)
In-Reply-To: <20190411015619.GA9198@richard>
Hi,
On 11/04/2019 03.56, Wei Yang wrote:
> On Mon, Apr 08, 2019 at 09:29:11PM +0000, Wei Yang wrote:
>>>>
>>>> Thomas,
>>>>
>>>> Thanks for pointing this out, while I have some different idea on how to fix
>>>> this.
>>>>
>>>> The reason of the core dump is errp already been set in
>>>> hotplug_handler_pre_plug(), and this function check acpi hotplug capability.
>>>> The order of this check is correct, while we should return when errp is set
>>>> in hotplug_handler_pre_plug().
>>>>
>>>> I got a fix like this, which I have tested and looks good to me.
>>>>
>>>>
>>>> diff --git a/hw/i386/pc.c b/hw/i386/pc.c
>>>> index 6077d27361..b11f3b15c1 100644
>>>> --- a/hw/i386/pc.c
>>>> +++ b/hw/i386/pc.c
>>>> @@ -2091,6 +2091,9 @@ static void pc_memory_pre_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
>>>> }
>>>>
>>>> hotplug_handler_pre_plug(pcms->acpi_dev, dev, errp);
>>>> + if (*errp) {
>>>> + return;
>>>> + }
>>>
>>> Not sure, but I think you can not rely on the fact that the caller set
>>> *errp = NULL already... that's why it is more common to use a local_err
>>> variable and error_propagate() for such cases (which is what I did in my
>>> patch).
>>>
>>
>> Ok, that's fine for me.
>>
>>> Also, why don't you want the "nvdimm is not enabled: missing 'nvdimm' in
>>> '-M'" check to be done first?
>>>
>>
>> Because this function pc_memory_pre_plug() will be called not only when
>> nvdimm is hot-plugged but also dimm is hot-plugged. And
>> hotplug_handler_pre_plug() here is to check the acpi(if it has) hot-plug
>> capability.
>>
>> So the check in pc_memory_pre_plug() is from generic to specific:
>> 1. Do we have capability to hot-plug?
>> 2. If the device is nvdimm, do we enabled nvdimm?
>>
>
> Thomas
>
> Do you think this is a reasonable explanation?
Fine for me, I don't mind either way as long as the crash is fixed. Feel
free to send a patch that restores the desired order.
Thomas
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Huth <thuth@redhat.com>
To: Wei Yang <richardw.yang@linux.intel.com>,
Wei Yang <richard.weiyang@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>,
Xiao Guangrong <xiaoguangrong.eric@gmail.com>
Subject: Re: [Qemu-devel] [PATCH for-4.0] hw/i386/pc: Fix crash when hot-plugging nvdimm on older machine types
Date: Thu, 11 Apr 2019 06:50:38 +0200 [thread overview]
Message-ID: <8c0c99e1-3f9c-f852-aa0d-7a4a31856392@redhat.com> (raw)
Message-ID: <20190411045038.MjrdBxbjL5GxbVtpGrjNXsZz6pFi4b6coly8TkZwMWY@z> (raw)
In-Reply-To: <20190411015619.GA9198@richard>
Hi,
On 11/04/2019 03.56, Wei Yang wrote:
> On Mon, Apr 08, 2019 at 09:29:11PM +0000, Wei Yang wrote:
>>>>
>>>> Thomas,
>>>>
>>>> Thanks for pointing this out, while I have some different idea on how to fix
>>>> this.
>>>>
>>>> The reason of the core dump is errp already been set in
>>>> hotplug_handler_pre_plug(), and this function check acpi hotplug capability.
>>>> The order of this check is correct, while we should return when errp is set
>>>> in hotplug_handler_pre_plug().
>>>>
>>>> I got a fix like this, which I have tested and looks good to me.
>>>>
>>>>
>>>> diff --git a/hw/i386/pc.c b/hw/i386/pc.c
>>>> index 6077d27361..b11f3b15c1 100644
>>>> --- a/hw/i386/pc.c
>>>> +++ b/hw/i386/pc.c
>>>> @@ -2091,6 +2091,9 @@ static void pc_memory_pre_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
>>>> }
>>>>
>>>> hotplug_handler_pre_plug(pcms->acpi_dev, dev, errp);
>>>> + if (*errp) {
>>>> + return;
>>>> + }
>>>
>>> Not sure, but I think you can not rely on the fact that the caller set
>>> *errp = NULL already... that's why it is more common to use a local_err
>>> variable and error_propagate() for such cases (which is what I did in my
>>> patch).
>>>
>>
>> Ok, that's fine for me.
>>
>>> Also, why don't you want the "nvdimm is not enabled: missing 'nvdimm' in
>>> '-M'" check to be done first?
>>>
>>
>> Because this function pc_memory_pre_plug() will be called not only when
>> nvdimm is hot-plugged but also dimm is hot-plugged. And
>> hotplug_handler_pre_plug() here is to check the acpi(if it has) hot-plug
>> capability.
>>
>> So the check in pc_memory_pre_plug() is from generic to specific:
>> 1. Do we have capability to hot-plug?
>> 2. If the device is nvdimm, do we enabled nvdimm?
>>
>
> Thomas
>
> Do you think this is a reasonable explanation?
Fine for me, I don't mind either way as long as the crash is fixed. Feel
free to send a patch that restores the desired order.
Thomas
next prev parent reply other threads:[~2019-04-11 4:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 9:23 [Qemu-devel] [PATCH for-4.0] hw/i386/pc: Fix crash when hot-plugging nvdimm on older machine types Thomas Huth
2019-04-07 9:23 ` Thomas Huth
2019-04-08 10:46 ` Paolo Bonzini
2019-04-08 10:46 ` Paolo Bonzini
2019-04-08 13:45 ` Wei Yang
2019-04-08 13:45 ` Wei Yang
2019-04-08 15:06 ` Thomas Huth
2019-04-08 15:06 ` Thomas Huth
2019-04-08 21:29 ` Wei Yang
2019-04-08 21:29 ` Wei Yang
2019-04-11 1:56 ` Wei Yang
2019-04-11 1:56 ` Wei Yang
2019-04-11 4:50 ` Thomas Huth [this message]
2019-04-11 4:50 ` Thomas Huth
2019-04-08 22:26 ` Eduardo Habkost
2019-04-08 22:26 ` Eduardo Habkost
2019-04-09 5:57 ` Markus Armbruster
2019-04-09 5:57 ` Markus Armbruster
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=8c0c99e1-3f9c-f852-aa0d-7a4a31856392@redhat.com \
--to=thuth@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.weiyang@gmail.com \
--cc=richardw.yang@linux.intel.com \
--cc=xiaoguangrong.eric@gmail.com \
/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).