Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp579140ybt; Fri, 19 Jun 2020 08:35:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy8ttpUAO8xJduEU8iiS1P3Z6K1dz5zngiDXABbCJUolD4scOekPz2OwFS2/yCKhTCxJMjz X-Received: by 2002:a17:906:6dcd:: with SMTP id j13mr3963534ejt.131.1592580923743; Fri, 19 Jun 2020 08:35:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592580923; cv=none; d=google.com; s=arc-20160816; b=Iopj8Efv/ZAk3idGyxU+Eg0vBvgh5l0YrsKVD4ZHeAcnfFl3IdoMmZAF8O1TXrKHsW kBzrw6wFyEDxEXN6iWQKqA4M+BaYYJ7CeDYWl39+MSFNI247JrTIiTDplh/MKMK6PmGa y0IjBBRl/IDF1Stj3e5WjtD0xcocDQO9L72uLq+wD6CXr75P7k+rkoTvJ0xD2yVcl5Ye yTCP3R6vZDoyKIdBTF77pxH9jWWky9keBP+GfzPhOwDdoI/XNS7gjQ9kKGtJejXbp/NJ iih187161QtsP1jeUGm9fnQAiWSd2nztU0ga0IARK2c5ZOR9sKsXrlTDmqPWVQS8CgqL a56A== 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=KTtzAIsEpySOhAgaJcc3X09SAmuSsBFqfLf6985W7PE=; b=cOlTTDrQX1cs/rc1hJp6xqZQlbC7NgDn5YnXuK9vC8LzxceylN+6AsU6U2FZ7pklxm Q+eqqCgUd5fPf1J78vpSL036kOVNiQ82oNHuejDKeIUUB0Af+p4zWEvDC+YbapxS6Gyy lzk+Gt4bApQOE/w76fhpquJ5LtFUI3WTkL7536EnPeKYJLDgK5Ho015VNeLYz6SDjJ2l zxH2IyfSKgHVq2/T/Emd7gmDhipwejcjIcGHjxecZPGaGSAnqsNPITtm3eakoviIwxRf PCYx4g/H9vXwzdV4oCAh8AT3h9d2kBOyzaSkdgNVq4PdUXAxDr2i8PGO0F1Sj6mrrBBc p5+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=I0ZyUg6o; 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 fi8si4039123ejb.641.2020.06.19.08.35.01; Fri, 19 Jun 2020 08:35:23 -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=I0ZyUg6o; 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 S2404644AbgFSPcY (ORCPT + 99 others); Fri, 19 Jun 2020 11:32:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:36024 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2393861AbgFSPcC (ORCPT ); Fri, 19 Jun 2020 11:32:02 -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 2245320757; Fri, 19 Jun 2020 15:32:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592580721; bh=DGPFRcC9pEulKheRi/94XpWnQZd9dykFl36awH9hWoY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=I0ZyUg6o64txPWwqvDDlN2CH8YU6SMTjVxRbu/gPUXY7Xa1M5bGNfaFwJEl92nOuT niRTKSpGwyDUlsI2bjMjLgvOvP1jhj6EO8mW+t5IhcBD5VA2W9TP9fpGP88Bc84XDk rkEEISH1AwKy3gwbX4Cn2DzJDwvDBZ1ttZGc+UiI= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Miquel Raynal Subject: [PATCH 5.7 358/376] mtd: rawnand: xway: Fix the probe error path Date: Fri, 19 Jun 2020 16:34:36 +0200 Message-Id: <20200619141727.263744438@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 34531be5e804a8e1abf314a6c3a19fe342e4a154 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-61-miquel.raynal@bootlin.com Signed-off-by: Greg Kroah-Hartman --- drivers/mtd/nand/raw/xway_nand.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/mtd/nand/raw/xway_nand.c +++ b/drivers/mtd/nand/raw/xway_nand.c @@ -210,7 +210,7 @@ static int xway_nand_probe(struct platfo err = mtd_device_register(mtd, NULL, 0); if (err) - nand_release(&data->chip); + nand_cleanup(&data->chip); return err; }