[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPybu_2cugVWwPwEHJktBzY8-a2PPEAVrWe5-A3sdN-zRkK1rA@mail.gmail.com>
Date: Fri, 12 Jun 2015 16:00:53 +0200
From: Ricardo Ribalda Delgado <ricardo.ribalda@...il.com>
To: Grant Likely <grant.likely@...aro.org>
Cc: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Pantelis Antoniou <pantelis.antoniou@...sulko.com>,
Wolfram Sang <wsa@...-dreams.de>,
Rob Herring <robh@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 2/2] drivercore: Fix unregistration path of platform devices
Hello
Tested-by: Ricardo Ribalda Delgado <ricardo.ribalda@...il.com>
Some runtime warnings, but no oops
[ 46.348911] Trying to free nonexistent resource
<00000000b0050000-00000000b005ffff>
[ 46.351979] Trying to free nonexistent resource
<00000000b9000000-00000000b900ffff>
[ 46.351993] Trying to free nonexistent resource
<00000000b0000000-00000000b000ffff>
[ 46.352003] Trying to free nonexistent resource
<00000000b9000000-00000000b900ffff>
[ 46.352009] Trying to free nonexistent resource
<00000000b0000000-00000000b000ffff>
Thanks!
On Sun, Jun 7, 2015 at 4:20 PM, Grant Likely <grant.likely@...aro.org> wrote:
> The unregister path of platform_device is broken. On registration, it
> will register all resources with either a parent already set, or
> type==IORESOURCE_{IO,MEM}. However, on unregister it will release
> everything with type==IORESOURCE_{IO,MEM}, but ignore the others. There
> are also cases where resources don't get registered in the first place,
> like with devices created by of_platform_populate()*.
>
> Fix the unregister path to be symmetrical with the register path by
> checking the parent pointer instead of the type field to decide which
> resources to unregister. This is safe because the upshot of the
> registration path algorithm is that registered resources have a parent
> pointer, and non-registered resources do not.
>
> * It can be argued that of_platform_populate() should be registering
> it's resources, and they argument has some merit. However, there are
> quite a few platforms that end up broken if we try to do that due to
> overlapping resources in the device tree. Until that is fixed, we need
> to solve the immediate problem.
>
> Cc: Pantelis Antoniou <pantelis.antoniou@...sulko.com>
> Cc: Wolfram Sang <wsa@...-dreams.de>
> Cc: Rob Herring <robh@...nel.org>
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Cc: Ricardo Ribalda Delgado <ricardo.ribalda@...il.com>
> Signed-off-by: Grant Likely <grant.likely@...aro.org>
> ---
> drivers/base/platform.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/base/platform.c b/drivers/base/platform.c
> index ebf034b97278..7403de94832c 100644
> --- a/drivers/base/platform.c
> +++ b/drivers/base/platform.c
> @@ -375,9 +375,7 @@ int platform_device_add(struct platform_device *pdev)
>
> while (--i >= 0) {
> struct resource *r = &pdev->resource[i];
> - unsigned long type = resource_type(r);
> -
> - if (type == IORESOURCE_MEM || type == IORESOURCE_IO)
> + if (r->parent)
> release_resource(r);
> }
>
> @@ -408,9 +406,7 @@ void platform_device_del(struct platform_device *pdev)
>
> for (i = 0; i < pdev->num_resources; i++) {
> struct resource *r = &pdev->resource[i];
> - unsigned long type = resource_type(r);
> -
> - if (type == IORESOURCE_MEM || type == IORESOURCE_IO)
> + if (r->parent)
> release_resource(r);
> }
> }
> --
> 2.1.4
>
--
Ricardo Ribalda
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists