From: Sasha Levin <sashal@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: patches@lists.linux.dev, stable@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
andersson@kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 6.17-5.4] pinctrl: qcom: make the pinmuxing strict
Date: Mon, 3 Nov 2025 19:28:34 -0500 [thread overview]
Message-ID: <aQlIsqXOBCy-qv_U@laps> (raw)
In-Reply-To: <1cd57f5c-d829-4dbd-aac9-b07d0e155e4e@oss.qualcomm.com>
On Thu, Oct 09, 2025 at 06:08:03PM +0200, Konrad Dybcio wrote:
>On 10/9/25 5:55 PM, Sasha Levin wrote:
>> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>>
>> [ Upstream commit cc85cb96e2e4489826e372cde645b7823c435de0 ]
>>
>> The strict flag in struct pinmux_ops disallows the usage of the same pin
>> as a GPIO and for another function. Without it, a rouge user-space
>> process with enough privileges (or even a buggy driver) can request a
>> used pin as GPIO and drive it, potentially confusing devices or even
>> crashing the system. Set it globally for all pinctrl-msm users.
>>
>> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>> Tested-by: Neil Armstrong <neil.armstrong@linaro.org>
>> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>> ---
>
>I didn't receive more related patches, but this had quite some
>dependencies (in pinctrl core and individual per-SoC drivers), which I'm
>not sure are worth all digging up and resolving conflicts
Dropped, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-11-04 0:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251009155752.773732-1-sashal@kernel.org>
2025-10-09 15:54 ` [PATCH AUTOSEL 6.17-6.6] power: supply: qcom_battmgr: handle charging state change notifications Sasha Levin
2025-10-09 15:55 ` [PATCH AUTOSEL 6.17-6.6] power: supply: qcom_battmgr: add OOI chemistry Sasha Levin
2025-10-09 15:55 ` [PATCH AUTOSEL 6.17-6.12] firmware: qcom: tzmem: disable sc7180 platform Sasha Levin
2025-10-09 15:55 ` [PATCH AUTOSEL 6.17-5.4] soc: qcom: smem: Fix endian-unaware access of num_entries Sasha Levin
2025-10-09 15:55 ` [PATCH AUTOSEL 6.17-5.4] pinctrl: qcom: make the pinmuxing strict Sasha Levin
2025-10-09 16:08 ` Konrad Dybcio
2025-11-04 0:28 ` Sasha Levin [this message]
2025-10-09 15:55 ` [PATCH AUTOSEL 6.17-6.16] firmware: qcom: scm: Allow QSEECOM on Dell Inspiron 7441 / Latitude 7455 Sasha Levin
2025-10-09 15:55 ` [PATCH AUTOSEL 6.17-6.12] firmware: qcom: scm: preserve assign_mem() error return value Sasha Levin
2025-10-09 15:56 ` [PATCH AUTOSEL 6.17-5.4] mmc: sdhci-msm: Enable tuning for SDR50 mode for SD card Sasha Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aQlIsqXOBCy-qv_U@laps \
--to=sashal@kernel.org \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=patches@lists.linux.dev \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).