Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp8380ybt; Tue, 23 Jun 2020 13:52:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxLhXDRHkdGRwE5zuEGrvJErMjWjcu6xttlvoEfza2aCN69mqj09/59t5LDu+17D2G2CSjn X-Received: by 2002:a17:906:f189:: with SMTP id gs9mr21508621ejb.203.1592945561472; Tue, 23 Jun 2020 13:52:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592945561; cv=none; d=google.com; s=arc-20160816; b=TBc1T89boEy/naJef9glALRIuhTI8uPGDdD4mkhrZnxIxxTYjsIMvurhwlPQHiCWtZ vaop4/+RplHYRYr+/dh54IOnPZ4nkAohnNzWPXdklcTvJJN0zD5MXN67lHIhL1bav9ag 2HAqUsBDOqOI5jK/qHmx59QU75UKpK1zro+tJUXZkBtcIzr8zMs0s8oBgnT3yBhltULw 4YHsHpu5eQKvaPklSST290hsRxYnymJXieHfRd7ri9d0Bng80mYf89kpMXs4avoApvns AntTRGIBCT+XU78iP/yEPEyjjGVrW9ELMcYHpLUs3+kKtTtJxDSkmF5j7xGCi2XuAH7r Ynpg== 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=DpHOYUaobPfGJ0SbS036IZ5NddvVzsdvRIBg05LWNqc=; b=V2hjLWHmMuba3aqtLVbtV/hxO+HgNyrF0hMGCCWKx+LQAvlLQh1wgkel+67Qe4zFXY jiZjFAvZfsofF2DCtZoho5nF17EEce3WXnMJfe0no4R6N+7RcfvgXlGqiC3xr9uGXx7H IYSRnLP8dPNDQ3xginxB3Y7GEJ3lXVbc6JEEErusGw/8bMLafuBXTDWzjhXDuZiVwNZN ui9sU0PyMSe57uAUyhyIxDJqihhmF3PNZrSpJqu17wJZ9FeVJLEZ8t7KKFuJ7sJ/F16a b6Pp9RKh/kV9/nLkMc//pM/DknOV35BASp3MjyvclJeD9X1e9KfKEoaqB45465foPAdH Ux2Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=iIPGo8Qo; 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 b10si1911576eja.426.2020.06.23.13.52.18; Tue, 23 Jun 2020 13:52:41 -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=iIPGo8Qo; 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 S2388106AbgFWUtA (ORCPT + 99 others); Tue, 23 Jun 2020 16:49:00 -0400 Received: from mail.kernel.org ([198.145.29.99]:48040 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404116AbgFWUsw (ORCPT ); Tue, 23 Jun 2020 16:48:52 -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 F003E2098B; Tue, 23 Jun 2020 20:48:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592945331; bh=2PrOR4tC0eomMZiJu+WKbx+KfKstrk/lQzhkYjghGxg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=iIPGo8Qo2ij+z09uq7cLsOBd13MIGC2+Wz6qom/5EBwhV3VBn/Mby3cE7VZdXkoBy joiYbOF9UAf5xRVcy79Sc2BQTfn8qW5BE5TQlzUE6h1G2GaDptpoKl2PaJ57kenpGu 8I2v7FYGGxyLl8odOuPXn3a9jgwoex/CVQsyESvI= 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 128/136] mtd: rawnand: mtk: Fix the probe error path Date: Tue, 23 Jun 2020 21:59:44 +0200 Message-Id: <20200623195310.249981499@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 8a82bbcadec877f5f938c54026278dfc1f05a332 ] 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: Sasha Levin --- drivers/mtd/nand/mtk_nand.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mtd/nand/mtk_nand.c b/drivers/mtd/nand/mtk_nand.c index 27fcce71ad38c..ff314ce104e58 100644 --- a/drivers/mtd/nand/mtk_nand.c +++ b/drivers/mtd/nand/mtk_nand.c @@ -1357,7 +1357,7 @@ static int mtk_nfc_nand_chip_init(struct device *dev, struct mtk_nfc *nfc, ret = mtd_device_parse_register(mtd, NULL, NULL, NULL, 0); if (ret) { dev_err(dev, "mtd parse partition error\n"); - nand_release(nand); + nand_cleanup(nand); return ret; } -- 2.25.1