Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp8221ybt; Tue, 23 Jun 2020 13:52:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxQTHk5vlxmfraxFVFI/HSJypO2p0kD5iL5vtYnITlmt4UpUilTt26zHLEgMWahaill/Agt X-Received: by 2002:a17:906:32d4:: with SMTP id k20mr20929997ejk.364.1592945546490; Tue, 23 Jun 2020 13:52:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592945546; cv=none; d=google.com; s=arc-20160816; b=rlGRucQOvSopb0X7lFAugCHUtNZczcwumi7ozi/fGCfFdHyvT4EZZFvmfBwd4OFMPR b42DFCHyWQFGpw4sIyjhIddtLQwNdxmZqyv2kC4NnuH2bCjgUlplTyN1Vr3MYZ42/lXS MKxQjGJ+Ss7JuZRfOJJQHRw2BSzsE35gfM7Q2o4o8wDxg3crBGkcaMXEfyIn/Ikyp20g zhb+yZuvabQ5XAXe+EEYdW4cqTPpv/DlIzi/RjT6SBtBdOgS4SCDqm+kwCQ3bP3oHz63 n9ruMRxg8FOvBVP6UNofp+2FSPFQB9bxps8v3r1pW2wJkpluwUWVnnRnlojPyFLPPQl7 nYjg== 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=2iGp0bImQPEDOZ+V8uvgkp947Czc2ad9k2a6QCrIeZw=; b=Hk8ZhZdISwxnAZCiqkeCYb+7FfRUU3BmQhFp42JAg+eZzy7LybqqKvadoC2egTxRCC 6HxJaagY1OC1+y8L3dVZlL5juEO69/PEZINyLbQbchL2ORKPgODOXaVvpjtL/C7y4Tg0 O4X7gicGZ9I4jKFcNG1rrwtyyuGaomqqLzgxWuAQvJWsuFzKXakQeUuVCR+TRyPdh+TV dklrIrBb7W4HodrGy657JVHZoN6/1mNbj9gsxJbsUdPEUijhNzkJvarJsRxq6mCSJYpf 5kLT0MQwZnaxgO71yfLBA29jURNwcYIax9m3hhbURlmUAhQu9Pjc2WEKcnSVJHzDcslp PLzQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=gGewX5VN; 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 i26si6256403ejy.58.2020.06.23.13.52.03; Tue, 23 Jun 2020 13:52:26 -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=gGewX5VN; 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 S2392950AbgFWUsj (ORCPT + 99 others); Tue, 23 Jun 2020 16:48:39 -0400 Received: from mail.kernel.org ([198.145.29.99]:47604 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2392938AbgFWUsa (ORCPT ); Tue, 23 Jun 2020 16:48:30 -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 BAAD5217D8; Tue, 23 Jun 2020 20:48:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592945311; bh=/8gCY5X9pERgShbmmKJyfJr5Kwu2OB8VA3tfZ/WPk7k=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=gGewX5VNEZLI6upEkBogkggUSk0fCEy3FGAplXmm76qfU5n1OtYOF+9Usdac9wzdn HNjju/O5UHi+iw53WUzTiLDz/t4D+bSVCwBNUi5bHMreMoVj0G4jsbL0E3m6b6alO0 8m0k2tMJUjdGRop75JO6htPI34K/qtyJNx65Eatg= 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 121/136] mtd: rawnand: sharpsl: Fix the probe error path Date: Tue, 23 Jun 2020 21:59:37 +0200 Message-Id: <20200623195309.825152891@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 0f44b3275b3798ccb97a2f51ac85871c30d6fbbc ] nand_release() is supposed be called after MTD device registration. Here, only nand_scan() happened, so use nand_cleanup() instead. There is no Fixes tag applying here as the use of nand_release() in this driver predates by far 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. 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-49-miquel.raynal@bootlin.com Signed-off-by: Sasha Levin --- drivers/mtd/nand/sharpsl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mtd/nand/sharpsl.c b/drivers/mtd/nand/sharpsl.c index 6cfff0c81153f..c245d66609c1f 100644 --- a/drivers/mtd/nand/sharpsl.c +++ b/drivers/mtd/nand/sharpsl.c @@ -192,7 +192,7 @@ static int sharpsl_nand_probe(struct platform_device *pdev) return 0; err_add: - nand_release(this); + nand_cleanup(this); err_scan: iounmap(sharpsl->io); -- 2.25.1