Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp9723ybt; Tue, 23 Jun 2020 13:55:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyqpVpJeKtX+RLBgrUEhvL4UGb3P6aK+BQDS0VTb0g95/aJhHHJU6BuCNMEmQBTjIe1gzVT X-Received: by 2002:a17:906:af83:: with SMTP id mj3mr755686ejb.470.1592945707369; Tue, 23 Jun 2020 13:55:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592945707; cv=none; d=google.com; s=arc-20160816; b=udFNFpJHTHvNr8JeYzOQeA/5ilWL838TUUFC2GNsCzyTO/cudVz5pQyU0WCBWNBHPd IrGLzX8HW7CujPihoxOb+NN1LnTzLy+njSXmUuxWVTJzMOnTKD+YhDZ8QE56bpT5azjg hDNBO2acQ1YHp7A2F5qekaD7NZWEtvQ4/25avyHdwZdW6WgYmpeCWBdbn5lHXFntj4dJ vmfnOZkJnGNSjhCgUtMD7e5BZzj+z74fMDw2a8ZRsci+LaQQ/EdAxH2sK1b7U0AeFc6y C0EYmz2svfjxyQs0kT6r14Q42KGxhbXcNcb1IppohUFYz9iO44MZxKDAshdVszpv1CbU tmWA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=2xP11PXyfLqf4h5WJEPPgoM32b5sqeiePxjHaoiLyRY=; b=Rf66v8O1CYeZ2TOwoHSgWjmRNm+7eDpCn7X+DUFAY7Gk3JXz8TVnOQO2N0EuKXjPGY wU9Dcd29jgD7oZ6iu5FPnQD6CKkiob3Ncrv/BD9maj+4oPjZsQVrykYp8odWyx1H+xr1 uT8Mowtyl5Du0+tYWlBYu4oFCEfAEhSW6xNqDNtP0p7mwacw2AVHYi2kmIcLsD5wjKc2 Qguur9F005YAK3XWbPxyph65HwQYNqiS6yQnIvdl8lz6Duxb9B6z5GdQMESDzxNrtIYT +P65TO1fPKtv+40um02MN1QsWJYAn8XQ/WxQca6hoCpzVa8ARRnymsDrjob/mrIAbPaw kLkw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ja+3G3WI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t16si10990795eju.162.2020.06.23.13.54.44; Tue, 23 Jun 2020 13:55:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ja+3G3WI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2392709AbgFWUu6 (ORCPT + 99 others); Tue, 23 Jun 2020 16:50:58 -0400 Received: from mail.kernel.org ([198.145.29.99]:47654 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390269AbgFWUsd (ORCPT ); Tue, 23 Jun 2020 16:48:33 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5B4E621582; Tue, 23 Jun 2020 20:48:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592945313; bh=sF7PcTMMH1d2H0pPutO5VZxqofV3Hyn8GCLsRR8cK18=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ja+3G3WIzVQhoH0+MUYaOlW+Epn6l2uz2f5lMnzFkY97zytG0iMUrA5NUk7uW+e1D NSwQR5vZf7X9HBcJsOypD/uy0CDLHxdgVW0BxuygNUouUrLMmbT3sB6xAH40Pq3/Ka /EjUTwgxR0/gzlcpzjEybNlfE+0LNUBSAwCBP9gI= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Miquel Raynal , Sasha Levin Subject: [PATCH 4.14 122/136] mtd: rawnand: xway: Fix the probe error path Date: Tue, 23 Jun 2020 21:59:38 +0200 Message-Id: <20200623195309.881567612@linuxfoundation.org> X-Mailer: git-send-email 2.27.0 In-Reply-To: <20200623195303.601828702@linuxfoundation.org> References: <20200623195303.601828702@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Miquel Raynal [ Upstream commit 34531be5e804a8e1abf314a6c3a19fe342e4a154 ] nand_release() is supposed be called after MTD device registration. Here, only nand_scan() happened, so use nand_cleanup() instead. There is no real Fixes tag applying here as the use of nand_release() in this driver predates the introduction of nand_cleanup() in commit d44154f969a4 ("mtd: nand: Provide nand_cleanup() function to free NAND related resources") which makes this change possible. However, pointing this commit as the culprit for backporting purposes makes sense even if this commit is not introducing any bug. Fixes: d44154f969a4 ("mtd: nand: Provide nand_cleanup() function to free NAND related resources") Signed-off-by: Miquel Raynal Cc: stable@vger.kernel.org Link: https://lore.kernel.org/linux-mtd/20200519130035.1883-61-miquel.raynal@bootlin.com Signed-off-by: Sasha Levin --- drivers/mtd/nand/xway_nand.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mtd/nand/xway_nand.c b/drivers/mtd/nand/xway_nand.c index 1988bb943d1bc..176a94fa31d7f 100644 --- a/drivers/mtd/nand/xway_nand.c +++ b/drivers/mtd/nand/xway_nand.c @@ -211,7 +211,7 @@ static int xway_nand_probe(struct platform_device *pdev) err = mtd_device_register(mtd, NULL, 0); if (err) - nand_release(&data->chip); + nand_cleanup(&data->chip); return err; } -- 2.25.1