Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp1769959ybl; Sat, 11 Jan 2020 02:27:52 -0800 (PST) X-Google-Smtp-Source: APXvYqxoeju4RVw4ouz2x+AR1XAYx1JHeb4eGEiRLyuRBk8HHMr+TE6l5E+kiRLW1EFaLa6S9dSu X-Received: by 2002:aca:c3c4:: with SMTP id t187mr5999354oif.89.1578738472423; Sat, 11 Jan 2020 02:27:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578738472; cv=none; d=google.com; s=arc-20160816; b=KXWasXeiHYiwqtpUqv9kAY1H64GjoCIzGSDJ3/QuduDTFxBivUEmu5LIAl/NRUhtq7 cK2ldqgL0doNGul+1Dfe1DkH71Z9JVOwFPZCky9FhAEkJIlbqVhG0xP8ivBbeDUUSYoi QoIVc1Mo5R5/e4RLf+X/lA7dqTiqtezvWnLr1q9TMx5/dg2qHmM7rUE7rWh7CSvOmlui 4EvMHIZdieh3ATQFDguT6dr4PjigkFKgxM9hKVPU78SLAMRq+baSSGFVElSM3C7bq2Lh vWOhG5psGN6h6x0GysUQlQAmZa8zlfIUmeOn3MnH8aOFFCwVe1gQZ9AeJ7IF62O0kUqU I62A== 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=pE0PX13b/FqYI1ES78i5BcfOxbAZveU1xQsaRVG23CY=; b=qGa5KxGO4w16BUcqrJDjfcxeqfDH+k3W36U2ENn4sdYxGlPBA7mv2vyfkCQp/aihX0 X12bwbgXIR3rriGj63A63n5ab6rBDq29vqPAY2hrsnGBf/3rLmpyxt658Fu9za++iJzF MAsWty9c+UhMYDy7XC9SRkVlurMw6TAt0aSfrBtLuDmWmJAgLai0hvnYb2Ea10kwPGS0 3JOg/odBpEUaKKWiRIWmF84pBZX4MbvwxuAc07pkEptrULppkC1rHjhpEiGliYd5U3xu LJ4tRnNXxNHdMPqJcKaX9YR22eoUY6ld3FCcrlD2Bkt8M6UIMr+BANARog1iLjZgtWQZ ZMzg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=krSYtTid; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v202si2966051oie.79.2020.01.11.02.27.40; Sat, 11 Jan 2020 02:27:52 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=krSYtTid; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731044AbgAKK0v (ORCPT + 99 others); Sat, 11 Jan 2020 05:26:51 -0500 Received: from mail.kernel.org ([198.145.29.99]:60006 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729122AbgAKK0t (ORCPT ); Sat, 11 Jan 2020 05:26:49 -0500 Received: from localhost (unknown [62.119.166.9]) (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 3802620842; Sat, 11 Jan 2020 10:26:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1578738409; bh=ASl7vaeg61VjfA/PHCSfSIa3DQSAHBoCvHj2gUv6USs=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=krSYtTidBJZ4Vze+pY5F5Wob7FBUEwhSdBwhDAmsMBUieuneIraBODTILl6GqWWuV zcaCwzTgXakGLs5thgcm77ShxWJWubkBdM/iV/VrR7CCX11aGKft635moIVFPppWb6 2i7ZsZHeFnwB1Cfv2JKYA2Kyy7u16vSMlnKuVJog= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Alexandre Torgue , Linus Walleij , Sasha Levin Subject: [PATCH 5.4 071/165] pinctrl: pinmux: fix a possible null pointer in pinmux_can_be_used_for_gpio Date: Sat, 11 Jan 2020 10:49:50 +0100 Message-Id: <20200111094927.093723511@linuxfoundation.org> X-Mailer: git-send-email 2.24.1 In-Reply-To: <20200111094921.347491861@linuxfoundation.org> References: <20200111094921.347491861@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: Alexandre Torgue [ Upstream commit 6ba2fd391ac58c1a26874f10c3054a1ea4aca2d0 ] This commit adds a check on ops pointer to avoid a kernel panic when ops->strict is used. Indeed, on some pinctrl driver (at least for pinctrl-stmfx) the pinmux ops is not implemented. Let's assume than gpio can be used in this case. Fixes: 472a61e777fe ("pinctrl/gpio: Take MUX usage into account") Signed-off-by: Alexandre Torgue Link: https://lore.kernel.org/r/20191204144106.10876-1-alexandre.torgue@st.com Signed-off-by: Linus Walleij Signed-off-by: Sasha Levin --- drivers/pinctrl/pinmux.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pinctrl/pinmux.c b/drivers/pinctrl/pinmux.c index e914f6efd39e..9503ddf2edc7 100644 --- a/drivers/pinctrl/pinmux.c +++ b/drivers/pinctrl/pinmux.c @@ -85,7 +85,7 @@ bool pinmux_can_be_used_for_gpio(struct pinctrl_dev *pctldev, unsigned pin) const struct pinmux_ops *ops = pctldev->desc->pmxops; /* Can't inspect pin, assume it can be used */ - if (!desc) + if (!desc || !ops) return true; if (ops->strict && desc->mux_usecount) -- 2.20.1