From: sashiko-bot@kernel.org
To: "Chaoyi Chen" <kernel@airkyi.com>
Cc: vkoul@kernel.org, neil.armstrong@linaro.org,
linux-phy@lists.infradead.org, dri-devel@lists.freedesktop.org,
olteanv@gmail.com
Subject: Re: [PATCH 2/5] drm/bridge: aux: Add drm_aux_bridge_register_from_node()
Date: Mon, 08 Jun 2026 07:17:28 +0000 [thread overview]
Message-ID: <20260608071728.F12911F00898@smtp.kernel.org> (raw)
In-Reply-To: <20260608070805.88-3-kernel@airkyi.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Missing `of_node_get()` on `np` causes an OF node reference count underflow when the device is unregistered or fails initialization.
--
commit cb36f8cc044a8e4dcecbd3dd967a5ee3d94e60aa
Author: Chaoyi Chen <chaoyi.chen@rock-chips.com>
drm/bridge: aux: Add drm_aux_bridge_register_from_node()
This patch introduces drm_aux_bridge_register_from_node() to allow
registering an aux bridge with a specific device node pointer. It refactors
drm_aux_bridge_register() to call this new function.
> diff --git a/drivers/gpu/drm/bridge/aux-bridge.c b/drivers/gpu/drm/bridge/aux-bridge.c
> --- a/drivers/gpu/drm/bridge/aux-bridge.c
> +++ b/drivers/gpu/drm/bridge/aux-bridge.c
[ ... ]
> @@ -62,7 +63,10 @@ int drm_aux_bridge_register(struct device *parent)
> adev->dev.parent = parent;
> adev->dev.release = drm_aux_bridge_release;
>
> - device_set_of_node_from_dev(&adev->dev, parent);
> + if (np)
> + device_set_node(&adev->dev, of_fwnode_handle(np));
> + else
> + device_set_of_node_from_dev(&adev->dev, parent);
>
> ret = auxiliary_device_init(adev);
> if (ret) {
> of_node_put(adev->dev.of_node);
[Severity: High]
Does this code introduce an OF node refcount underflow when np is provided?
When np is not NULL, device_set_node() is called, which simply assigns the
pointer without acquiring a reference. However, the else branch calls
device_set_of_node_from_dev(), which explicitly calls of_node_get().
If auxiliary_device_init() fails, the error path shown above unconditionally
calls of_node_put(adev->dev.of_node).
Similarly, when the device is destroyed, drm_aux_bridge_release() performs:
drivers/gpu/drm/bridge/aux-bridge.c:drm_aux_bridge_release() {
struct auxiliary_device *adev = to_auxiliary_dev(dev);
of_node_put(dev->of_node);
...
}
Will this lead to an unbalanced of_node_put() dropping a reference that was
never acquired when a specific device node pointer is passed?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260608070805.88-1-kernel@airkyi.com?part=2
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Chaoyi Chen" <kernel@airkyi.com>
Cc: vkoul@kernel.org, neil.armstrong@linaro.org,
linux-phy@lists.infradead.org, dri-devel@lists.freedesktop.org,
olteanv@gmail.com
Subject: Re: [PATCH 2/5] drm/bridge: aux: Add drm_aux_bridge_register_from_node()
Date: Mon, 08 Jun 2026 07:17:28 +0000 [thread overview]
Message-ID: <20260608071728.F12911F00898@smtp.kernel.org> (raw)
In-Reply-To: <20260608070805.88-3-kernel@airkyi.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Missing `of_node_get()` on `np` causes an OF node reference count underflow when the device is unregistered or fails initialization.
--
commit cb36f8cc044a8e4dcecbd3dd967a5ee3d94e60aa
Author: Chaoyi Chen <chaoyi.chen@rock-chips.com>
drm/bridge: aux: Add drm_aux_bridge_register_from_node()
This patch introduces drm_aux_bridge_register_from_node() to allow
registering an aux bridge with a specific device node pointer. It refactors
drm_aux_bridge_register() to call this new function.
> diff --git a/drivers/gpu/drm/bridge/aux-bridge.c b/drivers/gpu/drm/bridge/aux-bridge.c
> --- a/drivers/gpu/drm/bridge/aux-bridge.c
> +++ b/drivers/gpu/drm/bridge/aux-bridge.c
[ ... ]
> @@ -62,7 +63,10 @@ int drm_aux_bridge_register(struct device *parent)
> adev->dev.parent = parent;
> adev->dev.release = drm_aux_bridge_release;
>
> - device_set_of_node_from_dev(&adev->dev, parent);
> + if (np)
> + device_set_node(&adev->dev, of_fwnode_handle(np));
> + else
> + device_set_of_node_from_dev(&adev->dev, parent);
>
> ret = auxiliary_device_init(adev);
> if (ret) {
> of_node_put(adev->dev.of_node);
[Severity: High]
Does this code introduce an OF node refcount underflow when np is provided?
When np is not NULL, device_set_node() is called, which simply assigns the
pointer without acquiring a reference. However, the else branch calls
device_set_of_node_from_dev(), which explicitly calls of_node_get().
If auxiliary_device_init() fails, the error path shown above unconditionally
calls of_node_put(adev->dev.of_node).
Similarly, when the device is destroyed, drm_aux_bridge_release() performs:
drivers/gpu/drm/bridge/aux-bridge.c:drm_aux_bridge_release() {
struct auxiliary_device *adev = to_auxiliary_dev(dev);
of_node_put(dev->of_node);
...
}
Will this lead to an unbalanced of_node_put() dropping a reference that was
never acquired when a specific device node pointer is passed?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260608070805.88-1-kernel@airkyi.com?part=2
next prev parent reply other threads:[~2026-06-08 7:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 7:08 [PATCH 0/5] drm/bridge: Implement generic USB Type-C DP HPD bridge Chaoyi Chen
2026-06-08 7:08 ` Chaoyi Chen
2026-06-08 7:08 ` Chaoyi Chen
2026-06-08 7:08 ` [PATCH 1/5] " Chaoyi Chen
2026-06-08 7:08 ` Chaoyi Chen
2026-06-08 7:08 ` Chaoyi Chen
2026-06-08 7:22 ` sashiko-bot
2026-06-08 7:22 ` sashiko-bot
2026-06-08 7:08 ` [PATCH 2/5] drm/bridge: aux: Add drm_aux_bridge_register_from_node() Chaoyi Chen
2026-06-08 7:08 ` Chaoyi Chen
2026-06-08 7:08 ` Chaoyi Chen
2026-06-08 7:17 ` sashiko-bot [this message]
2026-06-08 7:17 ` sashiko-bot
2026-06-08 7:08 ` [PATCH 3/5] phy: rockchip: phy-rockchip-typec: Add DRM AUX bridge Chaoyi Chen
2026-06-08 7:08 ` Chaoyi Chen
2026-06-08 7:08 ` Chaoyi Chen
2026-06-08 7:24 ` sashiko-bot
2026-06-08 7:24 ` sashiko-bot
2026-06-08 7:08 ` [PATCH 4/5] drm/rockchip: cdn-dp: Support handle lane info without extcon Chaoyi Chen
2026-06-08 7:08 ` Chaoyi Chen
2026-06-08 7:08 ` Chaoyi Chen
2026-06-08 7:22 ` sashiko-bot
2026-06-08 7:22 ` sashiko-bot
2026-06-08 7:08 ` [PATCH 5/5] drm/rockchip: cdn-dp: Add multiple bridges to support PHY port selection Chaoyi Chen
2026-06-08 7:08 ` Chaoyi Chen
2026-06-08 7:08 ` Chaoyi Chen
2026-06-08 7:22 ` sashiko-bot
2026-06-08 7:22 ` sashiko-bot
-- strict thread matches above, loose matches on Subject: below --
2026-05-21 3:28 [PATCH 0/5] drm/bridge: Implement generic USB Type-C DP HPD bridge Chaoyi Chen
2026-05-21 3:28 ` [PATCH 2/5] drm/bridge: aux: Add drm_aux_bridge_register_from_node() Chaoyi Chen
2026-05-21 3:28 ` Chaoyi Chen
2026-05-21 3:28 ` Chaoyi Chen
2026-05-21 4:53 ` sashiko-bot
2026-06-01 22:27 ` Sebastian Reichel
2026-06-01 22:27 ` Sebastian Reichel
2026-06-01 22:27 ` Sebastian Reichel
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=20260608071728.F12911F00898@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@airkyi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.