From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 93C4017591; Tue, 26 Mar 2024 20:43:25 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711485805; cv=none; b=ulhF3ztb5dt0Bb5DCq/UqanOAoR9V8oljCp8X7RYbnHNXFxEdlIM5QbeW3wsvTNpTphYpQdWJoWp5Qs7SyK71dqEcNWgeMQ/mTu3tcbOQrCSfhUsbvFDAXPMaeZNqKf9ueBVnJK02KwR9otFj5QgLkGdn5T6uZMAeCSraMu+jwI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711485805; c=relaxed/simple; bh=SK4kbVI23QJSidrvvQmGhUSWkTsnFTBDfUyJyLO8ZLc=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=BMNORMxc9IzGRia0e55OX8HEP5JehY5UpAx/VOTLg70jkrFsOKqP796CFYRQzch7Zag8II2ZZiKztSd3J22yjliH6DK8QOAxUVwUXQrw4+VEfZK+7XQ6U/555hFs4xx754zl6vSBgaDfAIYLw9U+51egYQbaer3pUukHiyk/iak= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=T1zG7X3F; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="T1zG7X3F" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D0DF8C433C7; Tue, 26 Mar 2024 20:43:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1711485805; bh=SK4kbVI23QJSidrvvQmGhUSWkTsnFTBDfUyJyLO8ZLc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=T1zG7X3FsdrUOA8RBROUWxAURta4X2xmEopM/2AQfsExg9+HdxvwMh31OsWBsdWld 5A5yKq0cQF+S52QLaLfqg2I5cgx9pYlR44mKoQQ+IjXxZQj3GNvr826zovyj00zViF a3udcNZ5hfbUnZ5xnD7qd6NEvyFD0g57E1D1wdwlV6e5+xVAJicTSPbWbM6Ri/FaLB Pcf1YNWYAdqeA57trJw+P6zDKP6oju6s7JCHwsrWwEp+gGIVelQ7coeOBzeF3STI+R KQbZ4pGV+5BOeV9TQJg2USJHmpuDsnT2sv8oS9uHz+g0B6ktsHtpJooTsD+5CcCiTg kR6BbrYGaRkgA== Date: Tue, 26 Mar 2024 15:43:22 -0500 From: Rob Herring To: Herve Codina Cc: Greg Kroah-Hartman , "Rafael J. Wysocki" , Frank Rowand , Saravana Kannan , Lizhi Hou , Max Zhen , Sonal Santan , Stefano Stabellini , Jonathan Cameron , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Allan Nielsen , Horatiu Vultur , Steen Hegelund , Luca Ceresoli , Nuno Sa , Thomas Petazzoni Subject: Re: [PATCH v6 0/2] Synchronize DT overlay removal with devlink removals Message-ID: <20240326204322.GA3376856-robh@kernel.org> References: <20240325152140.198219-1-herve.codina@bootlin.com> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20240325152140.198219-1-herve.codina@bootlin.com> On Mon, Mar 25, 2024 at 04:21:24PM +0100, Herve Codina wrote: > Hi, > > In the following sequence: > of_platform_depopulate(); /* Remove devices from a DT overlay node */ > of_overlay_remove(); /* Remove the DT overlay node itself */ > > Some warnings are raised by __of_changeset_entry_destroy() which was > called from of_overlay_remove(): > ERROR: memory leak, expected refcount 1 instead of 2 ... > > The issue is that, during the device devlink removals triggered from the > of_platform_depopulate(), jobs are put in a workqueue. > These jobs drop the reference to the devices. When a device is no more > referenced (refcount == 0), it is released and the reference to its > of_node is dropped by a call to of_node_put(). > These operations are fully correct except that, because of the > workqueue, they are done asynchronously with respect to function calls. > > In the sequence provided, the jobs are run too late, after the call to > __of_changeset_entry_destroy() and so a missing of_node_put() call is > detected by __of_changeset_entry_destroy(). > > This series fixes this issue introducing device_link_wait_removal() in > order to wait for the end of jobs execution (patch 1) and using this > function to synchronize the overlay removal with the end of jobs > execution (patch 2). > > Compared to the previous iteration: > https://lore.kernel.org/linux-kernel/20240307111036.225007-1-herve.codina@bootlin.com/ > this v6 series: > - Add Saravana's 'Reviewed-by' tag > > This series handles cases reported by Luca [1] and Nuno [2]. > [1]: https://lore.kernel.org/all/20231220181627.341e8789@booty/ > [2]: https://lore.kernel.org/all/20240205-fix-device-links-overlays-v2-2-5344f8c79d57@analog.com/ > > Best regards, > Hervé > > Changes v5 -> v6 > - Patch 1 > Add 'Reviewed-by: Saravana Kannan ' > > - Patch 2 > No changes > > Changes v4 -> v5 > - Patch 1 > Remove the 'Fixes' tag > Add 'Tested-by: Luca Ceresoli ' > Add 'Reviewed-by: Nuno Sa ' > > - Patch 2 > Update comment as suggested > Add 'Reviewed-by: Saravana Kannan ' > Add 'Tested-by: Luca Ceresoli ' > Add 'Reviewed-by: Nuno Sa ' > > Changes v3 -> v4 > - Patch 1 > Uses flush_workqueue() instead of drain_workqueue(). > > - Patch 2 > Remove unlock/re-lock when calling device_link_wait_removal() > Move device_link_wait_removal() call to of_changeset_destroy() > Update commit log > > Changes v2 -> v3 > - Patch 1 > No changes > > - Patch 2 > Add missing device.h > > Changes v1 -> v2 > - Patch 1 > Rename the workqueue to 'device_link_wq' > Add 'Fixes' tag and Cc stable > > - Patch 2 > Add device.h inclusion. > Call device_link_wait_removal() later in the overlay removal > sequence (i.e. in free_overlay_changeset() function). > Drop of_mutex lock while calling device_link_wait_removal(). > Add 'Fixes' tag and Cc stable > > Herve Codina (2): > driver core: Introduce device_link_wait_removal() > of: dynamic: Synchronize of_changeset_destroy() with the devlink > removals > > drivers/base/core.c | 26 +++++++++++++++++++++++--- > drivers/of/dynamic.c | 12 ++++++++++++ > include/linux/device.h | 1 + > 3 files changed, 36 insertions(+), 3 deletions(-) Applied, thanks!