lkml.org 
[lkml]   [2014]   [Aug]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] resource: Fix the case of null pointer access
On Tue, Aug 12, 2014 at 04:49:35PM +0200, Richard Weinberger wrote:
> Am 12.08.2014 16:46, schrieb Vivek Goyal:
> > Richard and Daniel reported that UML is broken due to changes to resource
> > traversal functions. Problem is that iomem_resource.child can be null
> > and new code does not consider that possibility. Old code used a for loop
> > and that loop will not even execute if p was null.
> >
> > Revert back to for() loop logic and bail out if p is null.
> >
> > I also moved sibling_only check out of resource_lock. There is no
> > reason to keep it inside the lock.
> >
> > Following is backtrace of the UML crash.
>
> Shall I pickup this patch and route it via my uml tree to Linus?

I am fine with that.

Thanks
Vivek


\
 
 \ /
  Last update: 2014-08-12 17:21    [W:0.050 / U:0.144 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site