linux-kernel - Re: of: dynamic: resource: add WARN in release

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20150805140405.20ab09354f4123c561096eb8@linux-foundation.org>
Date:	Wed, 5 Aug 2015 14:04:05 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Robert ABEL <rabel@...-ec.uni-bielefeld.de>
Cc:	linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: of: dynamic: resource: add WARN in release_resource for DT
 overlays

On Thu, 30 Jul 2015 15:17:16 +0200 Robert ABEL <rabel@...-ec.uni-bielefeld.de> wrote:

> 
> This patch prevents a kernel OOPS when removing a DT overlay containing
> nodes with reg properties. release_resources is called for these nodes.
> However, the resource structs were never initialized, hence the kernel OOPS.
> 
> This is obviously a stopgap measure until a proper solution is coded, see [1].
> 
> 
> [1]: https://lkml.org/lkml/2014/4/17/359
>
> ...
>
> --- a/kernel/resource.c
> +++ b/kernel/resource.c
> @@ -236,6 +236,13 @@ static int __release_resource(struct resource *old)
>  {
>  	struct resource *tmp, **p;
>  
> +    /* devicetree overlays:
> +     * of code doesn't initialize parent, child, sibling
> +     * gracefully 'do the right thing' here
> +     */
> +	if (WARN(!old->parent, "%s: uninitialized resource %s\n", __FUNCTION__, old->name))
> +		return 0;
> +
>  	p = &old->parent->child;
>  	for (;;) {
>  		tmp = *p;

Can we please have a (much) better changelog for this?  Don't ask
people to go off and trawl through lkml.org threads (especially as
lkml.org seems to be down half the time).

What precisely is causing the crash, what are the plans to fix it, why
do we need a stopgap rather than fixing it properly, etc.

Why not put the workaround at the offending call site (whereever that
is?) rather than in the callee?

--
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/