linux-kernel - Re: "resource: provide new functions to walk through resources" breaks UML

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20140811122229.GA26869@redhat.com>
Date:	Mon, 11 Aug 2014 08:22:29 -0400
From:	Vivek Goyal <vgoyal@...hat.com>
To:	Richard Weinberger <richard@....at>
Cc:	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	user-mode-linux-devel <user-mode-linux-devel@...ts.sourceforge.net>,
	sahne@...0.at
Subject: Re: "resource: provide new functions to walk through resources"
 breaks UML

On Sun, Aug 10, 2014 at 06:56:14PM +0200, Richard Weinberger wrote:
> Hi Vivek,
> 
> Daniel Walter reported that UML is currently broken.
> The offending commit is:
> 

Hi Richard,

Thanks for pointing it out. I will look into it.

Would you have link to the report Daniel sent. I am interested in 
looking at backtrace.

Thanks
Vivek

> commit 8c86e70acead629aacb4afcd818add66bf6844d9
> Author: Vivek Goyal <vgoyal@...hat.com>
> Date:   Fri Aug 8 14:25:50 2014 -0700
> 
>     resource: provide new functions to walk through resources
> 
> It dies in next_resource():
>         /* Caller wants to traverse through siblings only */
>         if (sibling_only)
>                 return p->sibling;
> 
> because p is NULL.
> Please note that UML has no iomem, maybe this is the problem...
> 
> Thanks,
> //richard
--
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/