Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp2365891imm; Thu, 18 Oct 2018 13:26:10 -0700 (PDT) X-Google-Smtp-Source: ACcGV614V2xVKgRDcoOIpymSynBlsaxQ4gVFjjEnTH2+VdZB8UyQKsuyJESYAi/+BlHjUS3I02VP X-Received: by 2002:a65:4c43:: with SMTP id l3-v6mr4459624pgr.261.1539894370422; Thu, 18 Oct 2018 13:26:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539894370; cv=none; d=google.com; s=arc-20160816; b=D7RzwnA90ocJRN+LVxMBeu6ND/gh9mDpLwD/FsAltDnfXjvKIMn9IICPUFrFF6rKOT aQIZe9HEDRN1gbxFGjyuGxgKSl65y7LZRLHBAa/Jwn1nx/3D/IygMW+Axx4pSTwftvQt DauRo/Arcf8hh11SmmtdG4g27BD3FmYwt62U9kBnOXkc2OHlO1em23Cs/UOOy1tFm7w3 gG0IWhBujPsRGpZfIMPqxTBhlbp/xw2zNrBUWGtZw4nXGgawxNHmqruGRLTNB+d67qMj Ei/xBYHJTN0wc1+syhFdk9NKO0v5QDbgrcS6GXOQyVesbpf3g8LB/LDNlBQaiFTy7725 8ORw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=IWIAWbH5FdrSp/SAhxedey+yBG+groNreqgzEcQ1qc4=; b=HKG6ZojISn/KYqoHgK77TLoIdbqCv36CemPbNkbADQ7VxKY4IkFSe22u2i/wJCRXh+ lWaQZn1akTsw4A5/gI3o9Ql2C9SgNrO+x7o8ryRG3OceeBNHi+2FVymuKwO2BfLx0OhT /ZpNmHUlHbeKYGHedftQMXqDi0Rt96XBgUwL6L2V5hSz4Pf+SHh6VHTNPvTNuiMo5qFs vmazwOer2VdzEiulctdzThGZ52G+zFBkhqZOp081E8JIwOSpMD59vO0r5r68Ipzn1SFr HQuihfzyWuHA5KYGsZLjtFnymcK4A+G3Jilz49mLfGKsgDaqrf9Jwf6aiC1PiD2K9FIm WkiQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=IFzFophp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m13-v6si23034166pfd.123.2018.10.18.13.25.55; Thu, 18 Oct 2018 13:26:10 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=IFzFophp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727520AbeJSE2O (ORCPT + 99 others); Fri, 19 Oct 2018 00:28:14 -0400 Received: from mail.kernel.org ([198.145.29.99]:37856 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725735AbeJSE2N (ORCPT ); Fri, 19 Oct 2018 00:28:13 -0400 Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id CC18821486; Thu, 18 Oct 2018 20:25:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1539894332; bh=FijrFl+Jun+HKk+KfBRIss5bmX9j9o4cw4HezeO7mrc=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=IFzFophpyZ4gh4CxrP09E+Ad6cWJaEmZnk2qTOeLlrhbo4w1jRZURc2+dOGd1uNsR +hnBnF46tMlOq+yeipulnSXr0PgGlheZX9CuYeGKNWgEH/KwuP76QzSAd3Xjamb/7l niTfgjqQxli+Y0iScbYzwmpdiFtfV5wdBhaH256I= Received: by mail-ed1-f49.google.com with SMTP id z21-v6so29442484edb.11; Thu, 18 Oct 2018 13:25:31 -0700 (PDT) X-Gm-Message-State: ABuFfoiDfxj2pnjNDkSTt9GRqciILehoNnsjYHt7zVBNU8fTNlLDD57F EohG7qNuJdAz9hhf9Fpnm8fky7Q/hN+iaVuMKoA= X-Received: by 2002:a50:92fd:: with SMTP id l58-v6mr4468252eda.200.1539894330243; Thu, 18 Oct 2018 13:25:30 -0700 (PDT) MIME-Version: 1.0 References: <1539657458-24401-1-git-send-email-frowand.list@gmail.com> <1539657458-24401-2-git-send-email-frowand.list@gmail.com> In-Reply-To: From: Alan Tull Date: Thu, 18 Oct 2018 15:24:53 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v4 01/18] of: overlay: add tests to validate kfrees from overlay removal To: Frank Rowand Cc: Rob Herring , Pantelis Antoniou , Michael Ellerman , Benjamin Herrenschmidt , Paul Mackerras , Moritz Fischer , linux-kernel , linuxppc-dev , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , linux-fpga@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 17, 2018 at 4:30 PM Alan Tull wrote: > > On Mon, Oct 15, 2018 at 9:39 PM wrote: > > Hi Frank, > > > > > From: Frank Rowand > > > > Add checks: > > - attempted kfree due to refcount reaching zero before overlay > > is removed > > - properties linked to an overlay node when the node is removed > > - node refcount > one during node removal in a changeset destroy, > > if the node was created by the changeset > > > > After applying this patch, several validation warnings will be > > reported from the devicetree unittest during boot due to > > pre-existing devicetree bugs. The warnings will be similar to: > > > > OF: ERROR: of_node_release() overlay node /testcase-data/overlay-node/test-bus/test-unittest11/test-unittest111 contains unexpected properties > > OF: ERROR: memory leak - destroy cset entry: attach overlay node /testcase-data-2/substation@100/hvac-medium-2 expected refcount 1 instead of 2. of_node_get() / of_node_put() are unbalanced for this node. > > > > Signed-off-by: Frank Rowand > > --- > > Changes since v3: > > - Add expected value of refcount for destroy cset entry error. Also > > explain the cause of the error. > > > > drivers/of/dynamic.c | 29 +++++++++++++++++++++++++++++ > > drivers/of/overlay.c | 1 + > > include/linux/of.h | 15 ++++++++++----- > > 3 files changed, 40 insertions(+), 5 deletions(-) > > > > diff --git a/drivers/of/dynamic.c b/drivers/of/dynamic.c > > index f4f8ed9b5454..24c97b7a050f 100644 > > --- a/drivers/of/dynamic.c > > +++ b/drivers/of/dynamic.c > > @@ -330,6 +330,25 @@ void of_node_release(struct kobject *kobj) > > if (!of_node_check_flag(node, OF_DYNAMIC)) > > return; > > > > + if (of_node_check_flag(node, OF_OVERLAY)) { > > + > > + if (!of_node_check_flag(node, OF_OVERLAY_FREE_CSET)) { > > + /* premature refcount of zero, do not free memory */ > > + pr_err("ERROR: memory leak %s() overlay node %pOF before free overlay changeset\n", > > + __func__, node); > > + return; > > + } > > + > > + /* > > + * If node->properties non-empty then properties were added > > + * to this node either by different overlay that has not > > + * yet been removed, or by a non-overlay mechanism. > > + */ > > + if (node->properties) > > + pr_err("ERROR: %s() overlay node %pOF contains unexpected properties\n", > > + __func__, node); > > + } > > + > > property_list_free(node->properties); > > property_list_free(node->deadprops); > > > > @@ -434,6 +453,16 @@ struct device_node *__of_node_dup(const struct device_node *np, > > > > static void __of_changeset_entry_destroy(struct of_changeset_entry *ce) > > { > > + if (ce->action == OF_RECONFIG_ATTACH_NODE && > > + of_node_check_flag(ce->np, OF_OVERLAY)) { > > + if (kref_read(&ce->np->kobj.kref) > 1) { > > + pr_err("ERROR: memory leak - destroy cset entry: attach overlay node %pOF expected refcount 1 instead of %d. of_node_get() / of_node_put() are unbalanced for this node.\n", > > + ce->np, kref_read(&ce->np->kobj.kref)); > > Still testing as much as I have time to do. > > I'm hitting this error message once when removing an overlay that adds > several child nodes. The only node I get the message for was a node > that added a fixed-clock (the other nodes didn't trigger the error). > Then even if I edited all the rest of the overlay DTS and removed all > other child nodes and all references to the clock from other nodes, I > still got the error. > > Removing dtbo: 1-socfpga_arria10_socdk_sdmmc_ghrd_ovl_ext_cfg.dtb > [ 72.032270] OF: ERROR: memory leak - destroy cset entry: attach > overlay node /soc/base_fpga_region/clk_0 expected refcount 1 instead > of 2. of_node_get() / of_node_put() are unbalanced for this node. Update: with some helpful offline debug patches from Frank, I was able to find the source of the of_node_get/put unbalance. The fixed-rate clock driver calls of_clk_add_provider() when probed but never calls of_clk_del_provider() This patchset quite likely will uncover other of_node_get/put unbalances around the kernel. Alan > > Here's the very stripped down overlay: > > /dts-v1/; > /plugin/; > / { > fragment@0 { > target-path = "/soc/base_fpga_region"; > #address-cells = <1>; > #size-cells = <1>; > > __overlay__ { > external-fpga-config; > > #address-cells = <1>; > #size-cells = <1>; > > clk_0: clk_0 { > compatible = "fixed-clock"; > #clock-cells = <0>; > clock-frequency = <100000000>; /* 100.00 MHz */ > clock-output-names = "clk_0-clk"; > }; > }; > }; > };