Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp579466ybt; Fri, 19 Jun 2020 08:35:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwlbY1PBYNOhRLPRRhcVsBUI9dsgj4NdvGkNd7C4m7vnGWCo0nGMtzOx68avdat39/dZf+Z X-Received: by 2002:a05:6402:1d29:: with SMTP id dh9mr3852456edb.269.1592580949648; Fri, 19 Jun 2020 08:35:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592580949; cv=none; d=google.com; s=arc-20160816; b=A438iAWhrWkcVlGvCnHchp1Ey7ESGWL/KObAMKf3PIq2Wmet8brPGj9RP97TYB+7BH SQE+nWS1TsE14VvDqR3tQ0GgYHAFWDyhPXP9GArLDpbYfTpOUOs2KM7kIcMxyY/hpf1s g4YcToGSd9SEe/kc0Aofe/T8qpo8D+6BQ8Tc+ioUfTXJHj+euiRfhAsosouJdeHYD8Kv 1lixDCvYVKtzbYNwFZzhXVEx2toYT4Mn177Z35416YeDP3LEfaka6TECFI2E/eZtwPsR iU4bb5Udpmq2H3x14uno3n3fv5xtUMy1d78HgxPLvte5g/igTntR7UxxgOsDRXJ+AnsS QkHg== 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=MqQ7ypQjUYDHNg5FpvSVqqvRCduyWntukOZgCKYnfKE=; b=UQtTBKQ6hLZF4TgOKXmQKq3/hM4LPNX8j8AUe/sK56WTQ9iHjorU+fxZyf/PeE4QjN /sjMYpyvNUHkg3gAoE/o+O1b7Fqhs+KMmOwj6EwRhDKWf6jKAvWMAnjvfOTp0wwrRfST j3dBqIPGS0TTq1zfX/WGXLv/ZIUrgstPJgP1SGbxkxb6oLTsSftj6xGEUMVayzpK0Kby AZaR3qwkIPuUVm6vlv/w4zaQMTW0Fz2VHxktlpDHb1f/keVBywZ5mWSDkP9C+XNoQEi1 HsRicYj87iZUA+SFuK1xySbs93Y0WdVgCwc1uUlDPVoyiZvMFzzIS9JuJf75CR+WNyBX gmcA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=M5yjreBy; 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 m3si3820177ejr.329.2020.06.19.08.35.27; Fri, 19 Jun 2020 08:35:49 -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=M5yjreBy; 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 S2393934AbgFSPcx (ORCPT + 99 others); Fri, 19 Jun 2020 11:32:53 -0400 Received: from mail.kernel.org ([198.145.29.99]:36318 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404604AbgFSPcX (ORCPT ); Fri, 19 Jun 2020 11:32:23 -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 C98B620786; Fri, 19 Jun 2020 15:32:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592580742; bh=8suDrORI8J9gLI9SPd4KuWsQj2lnHj8vnNhBrFPsNgo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=M5yjreBywA+ZyMiOT19sycxHZrhOZvFX1MofSEc0f/Uv5pOViLFwu4Bw/Qq3wbNRq dfy7YYXZdpxCLxO/sIWnM/bILLVwZReJWFedaI/Yp4QL5fT/YZps6AsLjb67mQnmY0 KFiGMZiEDoyq8PDFpdZfCtoFaVTiYvtoWHBzP9OE= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Miquel Raynal Subject: [PATCH 5.7 365/376] mtd: rawnand: mtk: Fix the probe error path Date: Fri, 19 Jun 2020 16:34:43 +0200 Message-Id: <20200619141727.592220676@linuxfoundation.org> X-Mailer: git-send-email 2.27.0 In-Reply-To: <20200619141710.350494719@linuxfoundation.org> References: <20200619141710.350494719@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 commit 8a82bbcadec877f5f938c54026278dfc1f05a332 upstream. 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-28-miquel.raynal@bootlin.com Signed-off-by: Greg Kroah-Hartman --- drivers/mtd/nand/raw/mtk_nand.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/mtd/nand/raw/mtk_nand.c +++ b/drivers/mtd/nand/raw/mtk_nand.c @@ -1419,7 +1419,7 @@ static int mtk_nfc_nand_chip_init(struct ret = mtd_device_register(mtd, NULL, 0); if (ret) { dev_err(dev, "mtd parse partition error\n"); - nand_release(nand); + nand_cleanup(nand); return ret; }