From: Lee Jones <lee@kernel.org>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: linux-leds@vger.kernel.org, "Pavel Machek" <pavel@kernel.org>,
"Andrew Lunn" <andrew@lunn.ch>,
"Mike Marciniszyn" <mike.marciniszyn@gmail.com>,
"Jakub Kicinski" <kuba@kernel.org>, "Kees Cook" <kees@kernel.org>,
"Marek Behún" <kabel@kernel.org>,
"Christian Marangi" <ansuelsmth@gmail.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v4 1/4] leds: trigger: netdev: Put netdev on activate error path
Date: Thu, 15 Oct 2026 15:52:43 +0100 [thread overview]
Message-ID: <179198456306.839288.14631216021466477145@kernel.org> (raw)
In-Reply-To: <20261001131206.2513248-2-alexander.sverdlin@siemens.com>
On Thu, 01 Oct 2026, A. Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> When hw control is active, set_device_name() takes a reference on the
> netdev via dev_get_by_name(). The register_netdevice_notifier() failure
> path frees trigger_data without dropping it, leaking the netdev.
>
> Cc: stable@vger.kernel.org
> Closes: https://lore.kernel.org/all/20260914140045.B8F4C1F000FF@smtp.kernel.org/
> Fixes: 0316cc5629d1 ("leds: trigger: netdev: init mode if hw control already active")
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> ---
> Changelog:
> v3:
> - introduced unset_device_name() as a counterpart of set_device_name()
>
> drivers/leds/trigger/ledtrig-netdev.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/leds/trigger/ledtrig-netdev.c b/drivers/leds/trigger/ledtrig-netdev.c
> index 5b0132484594c..e2a6c95a0dc97 100644
> --- a/drivers/leds/trigger/ledtrig-netdev.c
> +++ b/drivers/leds/trigger/ledtrig-netdev.c
> @@ -324,6 +324,13 @@ static int set_device_name(struct led_netdev_data *trigger_data,
> return 0;
> }
>
> +static void unset_device_name(struct led_netdev_data *trigger_data)
> +{
> + dev_put(trigger_data->net_dev);
> + trigger_data->net_dev = NULL;
> + trigger_data->device_name[0] = 0;
> +}
Given that both callers immediately 'kfree(trigger_data)' after calling
this, why bother clearing these at all? Wouldn't calling 'dev_put()'
directly in 'netdev_trig_activate()' be simpler than introducing a
helper here?
> +
> static ssize_t device_name_store(struct device *dev,
> struct device_attribute *attr, const char *buf,
> size_t size)
> @@ -776,8 +783,10 @@ static int netdev_trig_activate(struct led_classdev *led_cdev)
> led_set_trigger_data(led_cdev, trigger_data);
>
> rc = register_netdevice_notifier(&trigger_data->notifier);
> - if (rc)
> + if (rc) {
> + unset_device_name(trigger_data);
> kfree(trigger_data);
> + }
>
> return rc;
> }
> @@ -790,7 +799,7 @@ static void netdev_trig_deactivate(struct led_classdev *led_cdev)
>
> cancel_delayed_work_sync(&trigger_data->work);
>
> - dev_put(trigger_data->net_dev);
> + unset_device_name(trigger_data);
>
> kfree(trigger_data);
> }
> --
> 2.55.0
>
--
Lee Jones
next prev parent reply other threads:[~2026-10-15 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 13:11 [PATCH v4 0/4] leds: trigger: netdev: fix sysfs_update_group() races A. Sverdlin
2026-10-01 13:12 ` [PATCH v4 1/4] leds: trigger: netdev: Put netdev on activate error path A. Sverdlin
2026-10-15 14:52 ` Lee Jones [this message]
2026-10-01 13:12 ` [PATCH v4 2/4] leds: trigger: netdev: Access net_dev under trigger_data->lock in the worker A. Sverdlin
2026-10-01 13:12 ` [PATCH v4 3/4] leds: trigger: netdev: Fix sysfs_update_group() races A. Sverdlin
2026-10-01 13:12 ` [PATCH v4 4/4] leds: trigger: netdev: Serialize mode/interval stores with trigger lock A. Sverdlin
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=179198456306.839288.14631216021466477145@kernel.org \
--to=lee@kernel.org \
--cc=alexander.sverdlin@siemens.com \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=kabel@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mike.marciniszyn@gmail.com \
--cc=pavel@kernel.org \
--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
all inboxes | Powered by JetHome®