From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752310AbdLEC0V (ORCPT ); Mon, 4 Dec 2017 21:26:21 -0500 Received: from mail.kernel.org ([198.145.29.99]:41426 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751582AbdLEC0T (ORCPT ); Mon, 4 Dec 2017 21:26:19 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B34B1219A4 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=robh+dt@kernel.org X-Google-Smtp-Source: AGs4zMbomLYoS43f6A02eokdyVHVD0DBkAHGnY7NPJIdFNWVp5CbljNx5jkpVm5ZZ0sV57F6oZuYft029FY1RLlWik4= MIME-Version: 1.0 In-Reply-To: References: <1512402456-8176-1-git-send-email-geert+renesas@glider.be> <1512402456-8176-3-git-send-email-geert+renesas@glider.be> From: Rob Herring Date: Mon, 4 Dec 2017 20:25:57 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 2/2] of: overlay: Fix cleanup order in of_overlay_apply() To: Geert Uytterhoeven Cc: Geert Uytterhoeven , Pantelis Antoniou , Frank Rowand , Colin King , Dan Carpenter , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 4, 2017 at 1:45 PM, Geert Uytterhoeven wrote: > Hi Rob, > > On Mon, Dec 4, 2017 at 8:35 PM, Rob Herring wrote: >> On Mon, Dec 4, 2017 at 9:47 AM, Geert Uytterhoeven >> wrote: >>> The special overlay mutex is taken first, hence it should be released >>> last in the error path. >>> >>> Move "mutex_lock(&of_mutex)" up, as suggested by Frank, as >>> free_overlay_changeset() should be called with that mutex held if any >>> non-trivial cleanup is to be done. >> >> Not holding the of_mutex for of_resolve_phandles is just wrong. >> Without it, a node and new phandle could be added via of_attach_node >> making the max phandle wrong. > > After my patch it's held, so what's the problem? There's no problem. Just highlighting the issue with the prior location is more than it seems from your explanation. Rob