Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp580579ybt; Fri, 19 Jun 2020 08:37:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx0b06xZKQvny3ftsWxQe406sGtQw0CnUbfig0eGdOuwmoh3JWPHDi+RGald2AG+5DpLXLH X-Received: by 2002:a05:6402:170d:: with SMTP id y13mr2578155edu.319.1592581047465; Fri, 19 Jun 2020 08:37:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592581047; cv=none; d=google.com; s=arc-20160816; b=S2V8JcCgswVxfWC3YzIZ0Lj5enTXH0vTtsh0qWOUSoF648FkiaR/cfCp7EzHGw7k1S hi8tOoRgR+KMxH+IsXcC4WQUmXh/nBEk/k4b2yqhRZumNzssxyBPtOMgXSjg3boF81fk uHqcV0j3ptUFrEAx/m4dfHKOC4LPr0oMcbnQjP9OPJerU+8TGrnAX+t1cNxEyjnGx3eT vVebdKBDRM205jCFZww7xmTHTruy8mTolaTUgORCJyegEqnKHrsuDS4jCr3jupYf6S6b o4kX/je51bQEVmz9EDd546bQxy2mxmJDk1P3R6YdVJlOJN5CPzEh136jMrD1E4lYjRZj zjdw== 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=t9R9wmjVQ+yIxLM7rfGMSONkf9IWm87xZh0ElE4oncQ=; b=g4U2s7Bvi0PCEnE0x1GNxmauX+EuC7ecxT01O0RyQaBKOHWPcylkj2TTaFfBig+5Vz 8E0fhANMulQjXbQrpSS8JBCkivssCRqYNBa2yHvA4Ow+VIoEamW089Fz6qYw3kou6qFG CAgLjZxGNBO5ulfqB8Ya4hjF/j8eO6h7Mc+KWb2Jpb4GSgqaFwyn001COOLZHZRNIQZN pjFYK8taZdcGBfPTWsbNRVMp63DNGmkrDwg1U+b2DhpngtgJAewVDynY0Xf+Fjx2CVOM f6jgj5POzYJalh5A6XN9+xHkr32NyegaqGX8N+Mao0IjHDaL9e5d0VQfmDQC2d+I0PJX TFoQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=rQ1TpP1+; 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 j17si3962298ejc.223.2020.06.19.08.37.04; Fri, 19 Jun 2020 08:37:27 -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=rQ1TpP1+; 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 S2393924AbgFSPcr (ORCPT + 99 others); Fri, 19 Jun 2020 11:32:47 -0400 Received: from mail.kernel.org ([198.145.29.99]:36382 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404675AbgFSPcZ (ORCPT ); Fri, 19 Jun 2020 11:32:25 -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 2E54220734; Fri, 19 Jun 2020 15:32:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592580744; bh=BUl86xW/ewJqWL8X0Gzx62jgAFsGACn6a8dbQ2QMsy0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=rQ1TpP1+d0kfnZUQyNxJUVgOjSODaOHrL0wtU1qlHXg+yCH1qHEubUOenus0dxBbz JJ+sWXbQb5hdfuJar1WDdsJ7U26uRXGGfF7qYZ2/8snPuG7aTi/TDohyeNK43UVAnm G0iBgZQ+pnE4rSPvZHNhAzGAiY8Ml51n1WOi9FBA= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Miquel Raynal Subject: [PATCH 5.7 366/376] mtd: rawnand: tmio: Fix the probe error path Date: Fri, 19 Jun 2020 16:34:44 +0200 Message-Id: <20200619141727.639185170@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 75e9a330a9bd48f97a55a08000236084fe3dae56 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-57-miquel.raynal@bootlin.com Signed-off-by: Greg Kroah-Hartman --- drivers/mtd/nand/raw/tmio_nand.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/mtd/nand/raw/tmio_nand.c +++ b/drivers/mtd/nand/raw/tmio_nand.c @@ -448,7 +448,7 @@ static int tmio_probe(struct platform_de if (!retval) return retval; - nand_release(nand_chip); + nand_cleanup(nand_chip); err_irq: tmio_hw_stop(dev, tmio);