Re: [Xen-devel] [PATCH 26/38] xen: xenbus: add missing put_devicecall

From: Ian Campbell
Date: Mon Jan 06 2014 - 05:00:53 EST


On Thu, 2014-01-02 at 13:53 +0000, David Vrabel wrote:
> On 19/12/13 15:03, Levente Kurusa wrote:
> > This is required so that we give up the last reference to the device.
> >
> > Signed-off-by: Levente Kurusa <levex@xxxxxxxxx>
> > ---
> > drivers/xen/xenbus/xenbus_probe.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/xen/xenbus/xenbus_probe.c b/drivers/xen/xenbus/xenbus_probe.c
> > index 3c0a74b..4abb9ee 100644
> > --- a/drivers/xen/xenbus/xenbus_probe.c
> > +++ b/drivers/xen/xenbus/xenbus_probe.c
> > @@ -465,8 +465,10 @@ int xenbus_probe_node(struct xen_bus_type *bus,
> >
> > /* Register with generic device framework. */
> > err = device_register(&xendev->dev);
> > - if (err)
> > + if (err) {
> > + put_device(&xendev->dev);
> > goto fail;
> > + }
> >
> > return 0;
> > fail:
>
> There is a kfree(xendev) here so this introduces a double-free.

How? put_device doesn't touch xendev itself, does it? It just drops the
ref on the dev member which is not separately dynamically allocated and
so not freed either.

Ian.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/