All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Marcel Apfelbaum <marcel@redhat.com>, qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC] pci: call PCIDeviceClass->exit on its .realize failure
Date: Mon, 19 Sep 2016 14:16:54 +0800	[thread overview]
Message-ID: <57DF82D6.4040902@cn.fujitsu.com> (raw)
In-Reply-To: <dae8c682-4b3d-fbc2-59d9-89fcc706db95@redhat.com>

Hi,
     sorry for replying late(was in vacation).

On 09/14/2016 07:59 PM, Marcel Apfelbaum wrote:
> On 09/14/2016 12:14 PM, Cao jin wrote:
>> It cannot guarantee all pci devices will free the allocated resource in
>> its .realize function on realize failure.
>>
>> CC: Michael S. Tsirkin <mst@redhat.com>
>> CC: Marcel Apfelbaum <marcel@redhat.com>
>> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
>> ---
>>
>> I found not all the devices will free the allocated resources on .realize
>> failure, and .exit function is the one who take responsibility to free
>> all
>> the resource. In theory, I think it should be PCIDeviceClass->exit who
>> does
>> the cleanup on realize failure, with appropriate check whether certain
>> resources is allocated.
>> It passed make check, but maybe need more confirmation, so, RFC.
>>

>
> Hi,
>
> I think the call to pc->exit is not necessary here.
>
> The call to pc->realize failed, so it is the callee (pc)
> responsibility to clean the resources.
>
> Please see in the same method:
>
>       pci_add_option_rom(pci_dev, is_default_rom, &local_err);
>          if (local_err) {
>              error_propagate(errp, local_err);
>              pci_qdev_unrealize(DEVICE(pci_dev), NULL);
>
>               ^^^^^^^^^^^^^^^^^^^
>
> This time we call pci_qdev_unrealize (that will call pc->exit)
> because pc->realize succeeded and it is now the caller responsibility
> to clean the resources.
>
>
> Have you found a specific scenario that causes problems?

No, it came to my mind when doing the patch "convert to error". Look 
usb_xhci_realize(), it will call usb_xhci_init to do some resource 
allocation, but won't free the resource once return because of 
msi_init's failure(that may be my fault), so the following patch[*] move 
it down.

I agree your view above. We can forget this patch:)

[*]http://lists.nongnu.org/archive/html/qemu-devel/2016-09/msg03063.html

-- 
Yours Sincerely,

Cao jin

      reply	other threads:[~2016-09-19  6:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  9:14 [Qemu-devel] [PATCH RFC] pci: call PCIDeviceClass->exit on its .realize failure Cao jin
2016-09-14 11:59 ` Marcel Apfelbaum
2016-09-19  6:16   ` Cao jin [this message]

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=57DF82D6.4040902@cn.fujitsu.com \
    --to=caoj.fnst@cn.fujitsu.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.