From: sashiko-bot@kernel.org
To: "AngeloGioacchino Del Regno" <angelogioacchino.delregno@collabora.com>
Cc: neil.armstrong@linaro.org, olteanv@gmail.com, vkoul@kernel.org,
linux-phy@lists.infradead.org
Subject: Re: [PATCH v12 06/12] spmi: Add helper to get a parent SPMI device
Date: Tue, 07 Jul 2026 11:27:56 +0000 [thread overview]
Message-ID: <20260707112756.DEAAB1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260707111829.180158-7-angelogioacchino.delregno@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Time-of-check to time-of-use (TOCTOU) race on `dev->parent` can lead to a NULL pointer dereference.
--
--- Patch [6]: [PATCH v12 06/12] spmi: Add helper to get a parent SPMI device ---
commit fb3218d6b528eabdc83ac90ed869685f4b9bd99e
Author: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
spmi: Add helper to get a parent SPMI device
This commit adds a new helper function spmi_get_parent_spmi_device()
which takes a struct device and returns a pointer to its parent SPMI
device if one exists, without modifying the reference count.
> diff --git a/drivers/spmi/spmi.c b/drivers/spmi/spmi.c
> index e218c81405458..a0a6ea9b1d2db 100644
> --- a/drivers/spmi/spmi.c
> +++ b/drivers/spmi/spmi.c
[ ... ]
> @@ -433,6 +433,29 @@ struct spmi_device *spmi_find_device_by_of_node(struct device_node *np)
> }
> EXPORT_SYMBOL_GPL(spmi_find_device_by_of_node);
>
> +/**
> + * spmi_get_parent_spmi_device() - get the parent SPMI device from current dev
> + * @dev: pointer to a subdevice on SPMI bus
> + *
> + * Checks if the passed device is a child of an SPMI device and returns a
> + * handle to the parent SPMI device without incrementing any refcount.
> + *
> + * Return: Handle to the parent SPMI device or NULL
> + */
> +struct spmi_device *spmi_get_parent_spmi_device(struct device *dev)
> +{
> + struct device *parent;
> +
> + if (dev && dev->parent) {
> + parent = dev->parent;
> +
> + if (parent->type == &spmi_dev_type)
[Severity: High]
Can a concurrent device topology change (like device_move()) cause a NULL
pointer dereference here?
If dev->parent is modified to NULL between the check in the if condition
and the assignment to the local parent variable, parent will become NULL
and this parent->type check will panic.
Since the compiler is permitted to emit two separate memory loads for
dev->parent in this sequence, would it be safer to read it exactly once
into the local variable before checking its validity?
> + return to_spmi_device(parent);
> + }
> + return NULL;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260707111829.180158-1-angelogioacchino.delregno@collabora.com?part=6
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-07-07 11:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 11:18 [PATCH v12 00/12] SPMI: Implement sub-devices and migrate drivers AngeloGioacchino Del Regno
2026-07-07 11:18 ` [PATCH v12 01/12] spmi: Fix potential use-after-free by grabbing of_node reference AngeloGioacchino Del Regno
2026-07-07 11:18 ` [PATCH v12 02/12] spmi: Remove redundant dev_name() print in spmi_device_add() AngeloGioacchino Del Regno
2026-07-07 11:18 ` [PATCH v12 03/12] spmi: Print error status with %pe format AngeloGioacchino Del Regno
2026-07-07 11:18 ` [PATCH v12 04/12] spmi: Remove unneeded goto in spmi_device_add() error path AngeloGioacchino Del Regno
2026-07-07 11:18 ` [PATCH v12 05/12] spmi: Implement spmi_subdevice_alloc_and_add() and devm variant AngeloGioacchino Del Regno
2026-07-07 11:31 ` sashiko-bot
2026-07-07 11:59 ` AngeloGioacchino Del Regno
2026-07-07 11:18 ` [PATCH v12 06/12] spmi: Add helper to get a parent SPMI device AngeloGioacchino Del Regno
2026-07-07 11:27 ` sashiko-bot [this message]
2026-07-07 11:57 ` AngeloGioacchino Del Regno
2026-07-07 11:18 ` [PATCH v12 07/12] nvmem: qcom-spmi-sdam: Migrate to devm_spmi_subdevice_alloc_and_add() AngeloGioacchino Del Regno
2026-07-07 11:18 ` [PATCH v12 08/12] power: reset: qcom-pon: " AngeloGioacchino Del Regno
2026-07-07 11:18 ` [PATCH v12 09/12] phy: qualcomm: eusb2-repeater: " AngeloGioacchino Del Regno
2026-07-07 11:18 ` [PATCH v12 10/12] misc: qcom-coincell: " AngeloGioacchino Del Regno
2026-07-07 11:18 ` [PATCH v12 11/12] iio: adc: qcom-spmi-iadc: " AngeloGioacchino Del Regno
2026-07-07 11:18 ` [PATCH v12 12/12] iio: adc: qcom-spmi-iadc: Remove regmap R/W wrapper functions AngeloGioacchino Del Regno
2026-07-07 13:18 ` [PATCH v12 00/12] SPMI: Implement sub-devices and migrate drivers Andy Shevchenko
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=20260707112756.DEAAB1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@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