Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753176AbbDTUgw (ORCPT ); Mon, 20 Apr 2015 16:36:52 -0400 Received: from mail-ig0-f170.google.com ([209.85.213.170]:35225 "EHLO mail-ig0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751745AbbDTUgt (ORCPT ); Mon, 20 Apr 2015 16:36:49 -0400 Date: Mon, 20 Apr 2015 15:36:45 -0500 From: Bjorn Helgaas To: Ricardo Ribalda Delgado Cc: Andrew Morton , Vivek Goyal , Vinod Koul , Cliff Wickman , Jiang Liu , Jakub Sitnicki , Thierry Reding , Mike Travis , LKML , Grant Likely Subject: Re: [PATCH] kernel/resource: Invalid memory access in __release_resource Message-ID: <20150420203645.GE20701@google.com> References: <1429546972-28400-1-git-send-email-ricardo.ribalda@gmail.com> <20150420192844.GD20701@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2484 Lines: 59 On Mon, Apr 20, 2015 at 10:24:25PM +0200, Ricardo Ribalda Delgado wrote: > Hi Bjorn! > > Thanks for your promtly response. > > On Mon, Apr 20, 2015 at 9:28 PM, Bjorn Helgaas wrote: > > [+cc Grant (author of ac80a51e2ce5)] > > > > Hi Ricardo, > > > > On Mon, Apr 20, 2015 at 06:22:52PM +0200, Ricardo Ribalda Delgado wrote: > >> > >> If of_platform_depopulate is called later, resource->parent is > >> accessed (Offset 0x30 of address 0), causing a kernel error. > > > > Interesting; how'd you find this? It looks like the > > of_platform_depopulate() code has been this way for a long time, so we > > must be doing something new that makes us trip over this now. More > > analysis below... > > I have an out of tree driver that dynamically adds devices to the device tree. > > It was developed before the dynamic_of and dt_overlays existed. Now I > am porting my code to the new interfaces available. I am trying to do > it small steps. > > First step was being able to depopulate a previously loaded device > tree. Old, code was calling of_platform_populate, so calling > of_platform_depopulate looked like the right choice. Unfortunately > everything crashed, and it turned out that this was the issue. > > On my defense I would say, that the plan is to make this driver > public, once the hardware is stabilized and sold to the public. No need to defend yourself; to me this looks like a bug in the of_platform code, so it's a good thing you tripped over it :) The obvious bug is the NULL pointer dereference. The not-quite-so- obvious bug is that I think the lack of insert_resource() means the resource tree (/proc/iomem, /proc/ioports) is missing some useful information. > > From reading drivers/base/platform.c, it looks like the intent is > > that platform device users would use these interfaces: > > I can take a look to modify OF to use insert_resource(), but I still > think that no matter what, we should add this extra check, like the > propossed patch or maybe with a BUG_ON().... I think it would be nicer to make OF use platform_device_add_resources() and platform_device_add() because then there's less duplication of code. But Grant might have had a reason for avoiding that. Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/