Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp893816ybt; Fri, 19 Jun 2020 17:14:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzl0KJZrxfNOBajINfl5SlVEqw316ENLe75p6atSYMwVkjg3BvaYPOy9AmwOF9MQ6lKsR8S X-Received: by 2002:a17:906:edb6:: with SMTP id sa22mr6230063ejb.393.1592612068525; Fri, 19 Jun 2020 17:14:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592612068; cv=none; d=google.com; s=arc-20160816; b=Nukpc2rTOgohd9HtzVdEsIXv6QI4RjrtWteRLLWm1OpliECLfQe9Al5g8dGvbhYr/f QmEIgTKlrmOXa+2GytFu0UM1Nc9629QO+fOUHC0unbOnRCS89yuxmSNfyJl7xExhx9PL 8jRPfBqC6gh8t3bHByWUAO42I4IrF+0ayrOHne0PDMcWC285E7hyXcoarVRiXL576jh/ 5GFeAeMTUg3QeSLJago9J1L/PIzomCES5gZxCF6B310ZsTj8NJHg1jrM954UVPBHKpAP FNUrmfjq38tdn3eNXO5cB4ABzilEybUE1o42eQ4aTz6cTqrv3PkA6suAMPHZEhBtWDp+ Tlcg== 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=psNGnWGMWghXe1dX44QEIpJQDBpuZVZySAa0gD8tPcQ=; b=bg8jL23ZxcXU7nafbMVDIMSr9KITXjQz9Gogji1m6uQZuzUcgcpLAkCzmfNXqXk32r 0FmYttznH1kgAqmdOXlzn57lVyBrcZS+C2ojylG4Cd9Qk6ExlSDxMFlZTR4O4lIYDP/z JDu/jFE272l+U3cf65g4cTfMqYflrt4i/2omHNt3y8V0ALMuxRF1gKn4nGqiTsdkL4bw 3vg/k5YI8pSNRuV8M8dxqB2iYSg+ZX0ob9OqESlQT8ST/FHeD1nuZvY5/BNj9I0uDtR0 8XgM38PSFdHfZa5JCTgT+1w6Wf5E1xx+XYd3MQd+TS6A1W62R5WkInh7p0+w3+mESQTE LVLQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=E8PhRvU6; 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 d24si159096ejb.602.2020.06.19.17.13.48; Fri, 19 Jun 2020 17:14:28 -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=E8PhRvU6; 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 S2393896AbgFSPce (ORCPT + 99 others); Fri, 19 Jun 2020 11:32:34 -0400 Received: from mail.kernel.org ([198.145.29.99]:36238 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2393679AbgFSPcR (ORCPT ); Fri, 19 Jun 2020 11:32:17 -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 5301220786; Fri, 19 Jun 2020 15:32:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592580736; bh=7RDSSuE0x1CRJMtpeeSsfflH94SQLQHmYsHUUAk+q2E=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=E8PhRvU6nmKBvOx7oDGZ6D43h9i/OZq6LKxovPXAoJE0HdWM7nSarOKXT2tsR229S lS0R0WZSLoZvhPhI8qvURn++G/cFPabocPw3G4FOUz8RfNx06EswDN7QjvY5dcbD8t JN8bmN88SKgemD6KwlUkKIR0W6Ll7CNsXS9J5l80= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Miquel Raynal Subject: [PATCH 5.7 363/376] mtd: rawnand: plat_nand: Fix the probe error path Date: Fri, 19 Jun 2020 16:34:41 +0200 Message-Id: <20200619141727.497380992@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 5284024b4dac5e94f7f374ca905c7580dbc455e9 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, hence pointing it as the commit to fix for backporting purposes, 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-43-miquel.raynal@bootlin.com Signed-off-by: Greg Kroah-Hartman --- drivers/mtd/nand/raw/plat_nand.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/mtd/nand/raw/plat_nand.c +++ b/drivers/mtd/nand/raw/plat_nand.c @@ -92,7 +92,7 @@ static int plat_nand_probe(struct platfo if (!err) return err; - nand_release(&data->chip); + nand_cleanup(&data->chip); out: if (pdata->ctrl.remove) pdata->ctrl.remove(pdev);