From: Paul Durrant <xadimgnik@gmail.com>
To: "'Markus Armbruster'" <armbru@redhat.com>, <qemu-devel@nongnu.org>
Cc: 'Anthony Perard' <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org,
'Stefano Stabellini' <sstabellini@kernel.org>,
'Gerd Hoffmann' <kraxel@redhat.com>
Subject: RE: [PATCH 02/11] xen: Fix and improve handling of device_add usb-host errors
Date: Mon, 27 Apr 2020 08:26:26 +0100 [thread overview]
Message-ID: <000501d61c65$2a65af30$7f310d90$@xen.org> (raw)
In-Reply-To: <20200424192027.11404-3-armbru@redhat.com>
> -----Original Message-----
> From: Markus Armbruster <armbru@redhat.com>
> Sent: 24 April 2020 20:20
> To: qemu-devel@nongnu.org
> Cc: Stefano Stabellini <sstabellini@kernel.org>; Anthony Perard <anthony.perard@citrix.com>; Paul
> Durrant <paul@xen.org>; Gerd Hoffmann <kraxel@redhat.com>; xen-devel@lists.xenproject.org
> Subject: [PATCH 02/11] xen: Fix and improve handling of device_add usb-host errors
>
> usbback_portid_add() leaks the error when qdev_device_add() fails.
> Fix that. While there, use the error to improve the error message.
>
> The qemu_opts_from_qdict() similarly leaks on failure. But any
> failure there is a programming error. Pass &error_abort.
>
> Fixes: 816ac92ef769f9ffc534e49a1bb6177bddce7aa2
> Cc: Stefano Stabellini <sstabellini@kernel.org>
> Cc: Anthony Perard <anthony.perard@citrix.com>
> Cc: Paul Durrant <paul@xen.org>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: xen-devel@lists.xenproject.org
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> hw/usb/xen-usb.c | 18 ++++++++----------
> 1 file changed, 8 insertions(+), 10 deletions(-)
>
> diff --git a/hw/usb/xen-usb.c b/hw/usb/xen-usb.c
> index 961190d0f7..42643c3390 100644
> --- a/hw/usb/xen-usb.c
> +++ b/hw/usb/xen-usb.c
> @@ -30,6 +30,7 @@
> #include "hw/usb.h"
> #include "hw/xen/xen-legacy-backend.h"
> #include "monitor/qdev.h"
> +#include "qapi/error.h"
> #include "qapi/qmp/qdict.h"
> #include "qapi/qmp/qstring.h"
>
> @@ -755,13 +756,15 @@ static void usbback_portid_add(struct usbback_info *usbif, unsigned port,
> qdict_put_int(qdict, "port", port);
> qdict_put_int(qdict, "hostbus", atoi(busid));
> qdict_put_str(qdict, "hostport", portname);
> - opts = qemu_opts_from_qdict(qemu_find_opts("device"), qdict, &local_err);
> - if (local_err) {
> - goto err;
> - }
> + opts = qemu_opts_from_qdict(qemu_find_opts("device"), qdict,
> + &error_abort);
> usbif->ports[port - 1].dev = USB_DEVICE(qdev_device_add(opts, &local_err));
> if (!usbif->ports[port - 1].dev) {
> - goto err;
> + qobject_unref(qdict);
> + xen_pv_printf(&usbif->xendev, 0,
> + "device %s could not be opened: %s\n",
> + busid, error_get_pretty(local_err));
> + error_free(local_err);
Previously the goto caused the function to bail out. Should there not be a 'return' here?
> }
> qobject_unref(qdict);
> speed = usbif->ports[port - 1].dev->speed;
> @@ -793,11 +796,6 @@ static void usbback_portid_add(struct usbback_info *usbif, unsigned port,
> usbback_hotplug_enq(usbif, port);
>
> TR_BUS(&usbif->xendev, "port %d attached\n", port);
> - return;
> -
> -err:
> - qobject_unref(qdict);
> - xen_pv_printf(&usbif->xendev, 0, "device %s could not be opened\n", busid);
> }
>
> static void usbback_process_port(struct usbback_info *usbif, unsigned port)
> --
> 2.21.1
next prev parent reply other threads:[~2020-04-27 7:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 19:20 [PATCH 00/11] More miscellaneous error handling fixes Markus Armbruster
2020-04-24 19:20 ` [PATCH 01/11] nvdimm: Plug memory leak in uuid property setter Markus Armbruster
2020-04-24 19:20 ` [PATCH 02/11] xen: Fix and improve handling of device_add usb-host errors Markus Armbruster
2020-04-27 7:26 ` Paul Durrant [this message]
2020-04-29 5:48 ` Markus Armbruster
2020-04-24 19:20 ` [PATCH 03/11] s390x/cpumodel: Fix harmless misuse of visit_check_struct() Markus Armbruster
2020-04-27 8:02 ` David Hildenbrand
2020-04-29 5:51 ` Markus Armbruster
2020-05-04 11:09 ` Cornelia Huck
2020-05-04 15:24 ` Markus Armbruster
2020-05-04 15:29 ` Cornelia Huck
2020-04-24 19:20 ` [PATCH 04/11] s390x/pci: Fix harmless mistake in zpci's property fid's setter Markus Armbruster
2020-04-27 14:11 ` Matthew Rosato
2020-04-27 14:40 ` Markus Armbruster
2020-04-24 19:20 ` [PATCH 05/11] tests/migration: Tighten error checking Markus Armbruster
2020-04-24 19:20 ` [PATCH 06/11] error: Use error_reportf_err() where appropriate Markus Armbruster
2020-04-24 20:08 ` Eric Blake
2020-04-27 8:53 ` Markus Armbruster
2020-04-27 9:26 ` Philippe Mathieu-Daudé
2020-04-27 13:59 ` Eric Blake
2020-04-24 19:20 ` [PATCH 07/11] mips/malta: Fix create_cps() error handling Markus Armbruster
2020-04-27 9:20 ` Philippe Mathieu-Daudé
2020-04-29 5:59 ` Markus Armbruster
2020-04-29 7:13 ` Philippe Mathieu-Daudé
2020-04-29 7:27 ` Markus Armbruster
2020-04-24 19:20 ` [PATCH 08/11] mips/boston: Fix boston_mach_init() " Markus Armbruster
2020-04-29 6:33 ` Markus Armbruster
2020-04-24 19:20 ` [PATCH 09/11] mips/boston: Plug memory leak in boston_mach_init() Markus Armbruster
2020-04-24 19:20 ` [PATCH 10/11] arm/sabrelite: Consistently use &error_fatal in sabrelite_init() Markus Armbruster
2020-04-27 9:17 ` Philippe Mathieu-Daudé
2020-04-24 19:20 ` [PATCH 11/11] i386: Fix x86_cpu_load_model() error API violation 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='000501d61c65$2a65af30$7f310d90$@xen.org' \
--to=xadimgnik@gmail.com \
--cc=anthony.perard@citrix.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=paul@xen.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).