Re: [PATCH v3 1/4] kernel/resource: Invalid memory access in __release_resource

2015-04-23 Thread Ricardo Ribalda Delgado
Hi Bjorn On Wed, Apr 22, 2015 at 6:47 PM, Bjorn Helgaas wrote: > > I'm not really a fan of this. The NULL pointer oops is a very good clue > all by itself, and it doesn't require any extra code here. It is a pointer to 0x30. For some reason my platform can handle a couple of oops, but if I ge

Re: [PATCH v3 1/4] kernel/resource: Invalid memory access in __release_resource

2015-04-22 Thread Bjorn Helgaas
On Wed, Apr 22, 2015 at 06:14:18PM +0200, Ricardo Ribalda Delgado wrote: > When a resource is initialized via of_platform_populate. > resource->parent is initialized to NULL via kzalloc. > (of_platform_populate->of_device_alloc->of_address_to_resource) > > If of_platform_depopulate is called later

[PATCH v3 1/4] kernel/resource: Invalid memory access in __release_resource

2015-04-22 Thread Ricardo Ribalda Delgado
When a resource is initialized via of_platform_populate. resource->parent is initialized to NULL via kzalloc. (of_platform_populate->of_device_alloc->of_address_to_resource) If of_platform_depopulate is called later, resource->parent is accessed (Offset 0x30 of address 0), causing a kernel error.