Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp580945ybt; Fri, 19 Jun 2020 08:38:00 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzXAcdexsLp7wrfNeUFs0W2/0DUcJ5RG4LILWe1SeWwaMpusesKihTZqEypSDx8yS8SbEOK X-Received: by 2002:a17:906:7e5a:: with SMTP id z26mr4351816ejr.263.1592581079997; Fri, 19 Jun 2020 08:37:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592581079; cv=none; d=google.com; s=arc-20160816; b=Xk2zKYe4TqoDUcBkPRZ+2y/+9iVHEvg2JOVIfqTOXw9AN5f++f+dqYwtHCx1ZIbQji WlIwBrK2MY0kNOEJldB3UNPQTyNEHamr38S4TYO986Xg3dik8X0xiUu2ZPZe7gkgCDaS If84W9EdPJBsSq/2LSalyTE4AcagC17t1fdRK6KoIarMRu8/ZmtSUv5khUOuUj/Ac4yk Xp/Mh0OSF567yr/gy5KZxXon9T6mh0NutZTMHu3cZEklRax4gtE/EegSB+Wls7QqxBs4 aL46RkQb3yLTW2sp9kqOclPhWajDBxvzC9Ifou+A16dEQLmUIy3jITCt4Z0qCxkXWd0m Jv1g== 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=BNjGaQ7imY1SvflTgt1yzZ3lZVgh3gCsEscS/03cqt8=; b=0YhStnigOqjp1yUV61MtShIL5Fztd0NKDZe0qxuc1BPwpxnD0ae9xUrBVK9wVg3BcA JTwp689LL1Jlqk8ievH/AG68dZMhXNNiwtBu1LWAWd77hba54sy8sa0PectIV5Gl4SN4 lrnHwn0LaiNHWH2oQmKmxM4CDPcBttpZwZwUAbblSgsLuW95p45EJlbJKxoeDZnAFyZW dTkFZllMXEZfxBGMMbGubWV5su8uoNJKk+6/dajxo7crEoblo/H+1Qu9geVJ6Nz/0bQB JGgfidj3e0sTdmarlgsVKj7JnbT1piYtUr6A5QErZj+W9FV4KRjBDZpES+etMF78qDK/ vWeg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="K/8agMGT"; 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 ds17si5128348ejc.619.2020.06.19.08.37.37; Fri, 19 Jun 2020 08:37:59 -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="K/8agMGT"; 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 S2404882AbgFSPe7 (ORCPT + 99 others); Fri, 19 Jun 2020 11:34:59 -0400 Received: from mail.kernel.org ([198.145.29.99]:36066 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2393862AbgFSPcE (ORCPT ); Fri, 19 Jun 2020 11:32:04 -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 920B220734; Fri, 19 Jun 2020 15:32:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592580724; bh=L6uAw5u2g44VN+ZMX5Ve2cEJ80HOp3drfSC9s8OfhG0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=K/8agMGTJdB/TdMjibp6/6gnCftg3IpjDgubfspjPYu0PYYa7IXNzNF9a57yNxQuR L+KjY1begHx3UEkv8DhHXdUXVfXwryPQ94fvXtmc2DiTLKv/nq35wTjRmN9j5ElTD7 OESyKDnb4+QKGWAdFiDjgVv+GPVlvhijVlhj4/Sw= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Miquel Raynal Subject: [PATCH 5.7 359/376] mtd: rawnand: orion: Fix the probe error path Date: Fri, 19 Jun 2020 16:34:37 +0200 Message-Id: <20200619141727.310370531@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 be238fbf78e4c7c586dac235ab967d3e565a4d1a 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 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 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-34-miquel.raynal@bootlin.com Signed-off-by: Greg Kroah-Hartman --- drivers/mtd/nand/raw/orion_nand.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/mtd/nand/raw/orion_nand.c +++ b/drivers/mtd/nand/raw/orion_nand.c @@ -180,7 +180,7 @@ static int __init orion_nand_probe(struc mtd->name = "orion_nand"; ret = mtd_device_register(mtd, board->parts, board->nr_parts); if (ret) { - nand_release(nc); + nand_cleanup(nc); goto no_dev; }