mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 (Meta)" <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
Subject: Re: [PATCH v6 0/5] leds: trigger: netdev: fix sysfs_update_group() races
Date: Fri, 13 Nov 2026 12:00:11 +0000	[thread overview]
Message-ID: <20261113120011.GG6323@joneslee-macbookpro.roam.internal> (raw)
In-Reply-To: <20261027113349.383147-1-alexander.sverdlin@siemens.com>

On Tue, 27 Oct 2026, A. Sverdlin wrote:

> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> 
> The netdev LED trigger refreshes the link_speed attribute group with
> sysfs_update_group() from several contexts (the NETDEV_CHANGE notifier,
> device_name writes and, indirectly, trigger (de)activation) that share no
> common lock. On a board that emits PHY link events while the trigger is
> being (re)armed during boot this is observed as a hard sysfs failure:
> 
>   sysfs: cannot create duplicate filename '...green:lan/link_10'
>   ...
>   led_trigger_set
>   led_trigger_write
> 
> The window between activate() and device_add_groups() in led_trigger_set()
> is narrow, so to reproduce it reliably I artificially widened it with the
> debug patch below:
> 
> --- a/drivers/leds/led-triggers.c
> +++ b/drivers/leds/led-triggers.c
> @@ -12,6 +12,7 @@
>  #include <linux/list.h>
>  #include <linux/spinlock.h>
>  #include <linux/device.h>
> +#include <linux/delay.h>
>  #include <linux/timer.h>
>  #include <linux/rwsem.h>
>  #include <linux/leds.h>
> @@ -223,6 +224,8 @@ int led_trigger_set(struct led_classdev *led_cdev, struct led_trigger *trig)
>  		if (ret)
>  			goto err_activate;
> 
> +		msleep(5000);
> +
>  		ret = device_add_groups(led_cdev->dev, trig->groups);
>  		if (ret) {
>  			dev_err(led_cdev->dev, "Failed to add trigger attributes\n");
> 
> With that msleep() in place, writing the trigger while a NETDEV_CHANGE is
> delivered from the linkwatch workqueue reproduces the duplicate-filename
> splat every time.
> 
> The whole series is LOCKDEP-verified.
> 
> Changelog:
> v6:
> - report invalid interval to user space
> - fixed unlocked hw_control check in interval_store()
> - added missing carrier_link_up check in netdev_trig_sw_blink()

This set is ready to apply, but needs a rebase.

Please add my RB on each patch when resending.

Acked-by: Lee Jones <lee@kernel.org>

> v5:
> - removed unset_device_name()
> - https://lore.kernel.org/all/20261020124651.1987272-1-alexander.sverdlin@siemens.com/
> v4:
> - introduced netdev_trig_sw_blink() and used it in netdev_trig_work()
> - https://lore.kernel.org/all/20261001131206.2513248-1-alexander.sverdlin@siemens.com/
> v3:
> - introduced unset_device_name() as a counterpart of set_device_name()
> - guard() has been converted to either explicit mutex_lock()/mutex_unlock()
>   or scoped_guard()
> - rebased onto next-20260925
> - https://lore.kernel.org/all/20260929120902.2793138-1-alexander.sverdlin@siemens.com/
> v2:
> - addressed pre-existing issues found by Sashiko (patches 1&2)
> - reduced verbosity both in comments and in commit messages
> - patch 3 is a combined rework of patches 1&2 from v1
> - dropped sync from cancel_delayed_work() (worker now takes the lock)
> - https://lore.kernel.org/all/20260921093249.3481413-1-alexander.sverdlin@siemens.com/
> v1:
> - https://lore.kernel.org/all/20260914132356.807004-1-alexander.sverdlin@siemens.com/
> 
> 
> Alexander Sverdlin (5):
>   leds: trigger: netdev: Put netdev on activate error path
>   leds: trigger: netdev: Access net_dev under trigger_data->lock in the
>     worker
>   leds: trigger: netdev: Fix sysfs_update_group() races
>   leds: trigger: netdev: Report invalid interval to user space
>   leds: trigger: netdev: Serialize mode/interval stores with trigger
>     lock
> 
>  drivers/leds/trigger/ledtrig-netdev.c | 140 ++++++++++++++++++--------
>  1 file changed, 96 insertions(+), 44 deletions(-)
> 
> -- 
> 2.56.0
> 
> 

-- 
Lee Jones

      parent reply	other threads:[~2026-11-13 12:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 11:33 A. Sverdlin
2026-10-27 11:33 ` [PATCH v6 1/5] leds: trigger: netdev: Put netdev on activate error path A. Sverdlin
2026-10-27 11:33 ` [PATCH v6 2/5] leds: trigger: netdev: Access net_dev under trigger_data->lock in the worker A. Sverdlin
2026-10-27 11:33 ` [PATCH v6 3/5] leds: trigger: netdev: Fix sysfs_update_group() races A. Sverdlin
2026-10-27 11:33 ` [PATCH v6 4/5] leds: trigger: netdev: Report invalid interval to user space A. Sverdlin
2026-10-30 13:23   ` Griffin Kroah-Hartman
2026-10-27 11:33 ` [PATCH v6 5/5] leds: trigger: netdev: Serialize mode/interval stores with trigger lock A. Sverdlin
2026-11-13 12:00 ` Lee Jones [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=20261113120011.GG6323@joneslee-macbookpro.roam.internal \
    --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 \
    /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®