From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Babanpreet Singh <bbnpreetsingh@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: Orson Zhai <orsonzhai@gmail.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: sprd-adi: Fix probe succeeding without registering the controller
Date: Mon, 27 Jul 2026 14:09:35 +0800 [thread overview]
Message-ID: <7792d078-f80e-42f4-9217-190ef5fb8573@linux.alibaba.com> (raw)
In-Reply-To: <20260726072221.7-1-bbnpreetsingh@gmail.com>
On 7/26/26 3:22 PM, Babanpreet Singh wrote:
> With CONFIG_HWSPINLOCK=n the of_hwspin_lock_get_id() stub returns 0
> unconditionally. In sprd_adi_probe() the guard
>
> if (ret > 0 || (IS_ENABLED(CONFIG_HWSPINLOCK) && ret == 0))
>
> is false for that 0, so it takes the else branch, where the switch has no
> case for 0 and lands in
>
> default:
> return dev_err_probe(&pdev->dev, ret, "failed to find hwlock id\n");
>
> dev_err_probe() returns its err argument unchanged, so probe logs
> "failed to find hwlock id" and then returns 0, reporting success.
> sprd_adi_hw_init(), the restart handler and devm_spi_register_controller()
> are all skipped: the device binds but no SPI controller is ever
> registered. Since the stub is a constant-returning static inline, the
> compiler folds the whole remainder of probe away as dead code - an
> object built in that configuration contains no reference to
> devm_spi_register_controller() at all.
>
> The hardware spinlock is optional for this controller and the -ENOENT arm
> already covers "no hardware spinlock supplied". Treat the stub's 0 the
> same way and continue without a lock; all four users of sadi->hwlock
> already test it for NULL.
>
> This is not reachable on production kernels. Kconfig has
>
> depends on HWSPINLOCK || (COMPILE_TEST && !HWSPINLOCK)
>
> so the affected configuration exists only under COMPILE_TEST, where no
> real hardware is present. Object code for CONFIG_HWSPINLOCK=y builds is
> byte-identical before and after this change.
>
> Found by smatch:
> drivers/spi/spi-sprd-adi.c:560 sprd_adi_probe() warn: passing zero to 'dev_err_probe'
>
> Fixes: f9adf61e983f ("spi: sprd: adi: Change hwlock to be optional")
> Assisted-by: Claude:claude-opus-5
> Signed-off-by: Babanpreet Singh <bbnpreetsingh@gmail.com>
> ---
> drivers/spi/spi-sprd-adi.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/spi/spi-sprd-adi.c b/drivers/spi/spi-sprd-adi.c
> index e7d83c16b46c..7c29115c5b8b 100644
> --- a/drivers/spi/spi-sprd-adi.c
> +++ b/drivers/spi/spi-sprd-adi.c
> @@ -553,6 +553,11 @@ static int sprd_adi_probe(struct platform_device *pdev)
> return -ENXIO;
> } else {
> switch (ret) {
> + case 0:
> + /*
> + * Only reachable with CONFIG_HWSPINLOCK=n, where the
> + * of_hwspin_lock_get_id() stub returns 0.
> + */
Please add a 'fallthrough' here. With that, you can add:
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> case -ENOENT:
> dev_info(&pdev->dev, "no hardware spinlock supplied\n");
> break;
prev parent reply other threads:[~2026-07-27 6:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 7:22 Babanpreet Singh
2026-07-27 6:09 ` Baolin Wang [this message]
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=7792d078-f80e-42f4-9217-190ef5fb8573@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=bbnpreetsingh@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=zhang.lyra@gmail.com \
/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
all inboxes | Powered by JetHome®