From: Lee Jones <lee@kernel.org>
To: lee@kernel.org
Cc: linux-kernel@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Ben Whitten <ben.whitten@gmail.com>,
Bryan Wu <cooloney@gmail.com>,
Christian Hitz <christian.hitz@bbv.ch>,
Christian Marangi <ansuelsmth@gmail.com>,
Daniel Mack <daniel@zonque.org>, Dan Murphy <dmurphy@ti.com>,
David Rivshin <drivshin@allworx.com>,
"David S. Miller" <davem@davemloft.net>,
Dmitry Antipov <dmantipov@yandex.ru>,
Eddie James <eajames@linux.ibm.com>,
Florian Fainelli <ffainelli@freebox.fr>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
John Lenz <lenz@cs.wisc.edu>,
Krzysztof Kozlowski <krzk@kernel.org>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-leds@vger.kernel.org, Luca Weiss <luca@lucaweiss.eu>,
Luis Henriques <lhenriques@suse.com>,
Nate Case <ncase@xes-inc.com>,
Nikita Travkin <nikitos.tr@gmail.com>,
Oliver Jowett <oliver@opencloud.com>,
Pavel Machek <pavel@kernel.org>,
Richard Purdie <rpurdie@openedhand.com>
Subject: [PATCH 00/21] leds: Assorted bug fixes across core, flash, trigger, and drivers
Date: Wed, 21 Oct 2026 12:32:09 +0000 [thread overview]
Message-ID: <20261021123406.3163547-1-lee@kernel.org> (raw)
These issues were reported by Sashiko.
This series addresses a collection of bugs across the LEDs subsystem,
including locking and concurrency fixes, device-tree node reference
leaks, out-of-bounds array accesses, divide-by-zero and current-limit
clamping issues, and devres lifecycle ordering fixes.
Cc: Andrew Lunn <andrew@lunn.ch>
Cc: Ben Whitten <ben.whitten@gmail.com>
Cc: Bryan Wu <cooloney@gmail.com>
Cc: Christian Hitz <christian.hitz@bbv.ch>
Cc: Christian Marangi <ansuelsmth@gmail.com>
Cc: Daniel Mack <daniel@zonque.org>
Cc: Dan Murphy <dmurphy@ti.com>
Cc: David Rivshin <drivshin@allworx.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Eddie James <eajames@linux.ibm.com>
Cc: Florian Fainelli <ffainelli@freebox.fr>
Cc: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: John Lenz <lenz@cs.wisc.edu>
Cc: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Kyungmin Park <kyungmin.park@samsung.com>
Cc: linux-leds@vger.kernel.org
Cc: Luca Weiss <luca@lucaweiss.eu>
Cc: Luis Henriques <lhenriques@suse.com>
Cc: Nate Case <ncase@xes-inc.com>
Cc: Nikita Travkin <nikitos.tr@gmail.com>
Cc: Oliver Jowett <oliver@opencloud.com>
Cc: Pavel Machek <pavel@kernel.org>
Cc: Richard Purdie <rpurdie@openedhand.com>
Lee Jones (21):
leds: lm3532: Propagate error from devm_regulator_get()
leds: lm3532: Use dev_err_probe() when lm3532_parse_node() fails
leds: trigger: netdev: Hold RTNL lock across hw_control_get_device()
in activate
leds: aw2013: Guard LED array index in aw2013_probe_dt()
leds: pca955x: Take a reference on the child firmware node
leds: lp50xx: Guard sub-LED count in lp50xx_probe_dt()
leds: trigger: netdev: Serialise work cancellation and state updates
leds: sgm3140: Replace powerdown timer with delayed work
leds: sgm3140: Cancel powerdown work via devres after LED
unregistration
leds: class: Initialise trigger_lock before exposing sysfs attributes
leds: class: Unlock led_access before unregistering device on error
leds: aat1290: Retain child device_node reference for device lifetime
leds: aat1290: Prevent out-of-bounds read in
aat1290_brightness_to_intensity()
leds: flash: Avoid divide-by-zero in led_clamp_align()
leds: lm3532: Validate LED string indices in lm3532_parse_node()
leds: lm3532: Clamp full-scale current to minimum bound
leds: aat1290: Avoid leaking devres pinctrl handles on strobe source
changes
leds: aw2013: Unlock chip mutex before registering LEDs
leds: is31fl32xx: Clamp channel current limit in is31fl3293_reset()
leds: flash: Terminate sysfs_groups array with NULL
leds: lm3692x: Use devm_mutex_init() to avoid premature mutex
destruction
drivers/leds/flash/leds-aat1290.c | 18 +++++++--
drivers/leds/flash/leds-sgm3140.c | 30 ++++++++------
drivers/leds/led-class-flash.c | 7 ++++
drivers/leds/led-class.c | 9 +++--
drivers/leds/leds-aw2013.c | 57 ++++++++++++++++-----------
drivers/leds/leds-is31fl32xx.c | 3 +-
drivers/leds/leds-lm3532.c | 33 +++++++++-------
drivers/leds/leds-lm3692x.c | 6 ++-
drivers/leds/leds-lp50xx.c | 8 ++++
drivers/leds/leds-pca955x.c | 19 +++++++--
drivers/leds/trigger/ledtrig-netdev.c | 43 ++++++++++++++------
11 files changed, 158 insertions(+), 75 deletions(-)
--
2.56.0.218.g1ec904b173-goog
next reply other threads:[~2026-10-21 12:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 12:32 Lee Jones [this message]
2026-10-21 12:32 ` [PATCH 01/21] leds: lm3532: Propagate error from devm_regulator_get() Lee Jones
2026-10-21 12:32 ` [PATCH 02/21] leds: lm3532: Use dev_err_probe() when lm3532_parse_node() fails Lee Jones
2026-10-21 12:32 ` [PATCH 03/21] leds: trigger: netdev: Hold RTNL lock across hw_control_get_device() in activate Lee Jones
2026-10-21 12:32 ` [PATCH 04/21] leds: aw2013: Guard LED array index in aw2013_probe_dt() Lee Jones
2026-10-21 12:32 ` [PATCH 05/21] leds: pca955x: Take a reference on the child firmware node Lee Jones
2026-10-21 12:32 ` [PATCH 06/21] leds: lp50xx: Guard sub-LED count in lp50xx_probe_dt() Lee Jones
2026-10-21 12:32 ` [PATCH 07/21] leds: trigger: netdev: Serialise work cancellation and state updates Lee Jones
2026-10-21 12:32 ` [PATCH 08/21] leds: sgm3140: Replace powerdown timer with delayed work Lee Jones
2026-10-21 12:32 ` [PATCH 09/21] leds: sgm3140: Cancel powerdown work via devres after LED unregistration Lee Jones
2026-10-21 12:32 ` [PATCH 10/21] leds: class: Initialise trigger_lock before exposing sysfs attributes Lee Jones
2026-10-21 12:32 ` [PATCH 11/21] leds: class: Unlock led_access before unregistering device on error Lee Jones
2026-10-21 12:32 ` [PATCH 12/21] leds: aat1290: Retain child device_node reference for device lifetime Lee Jones
2026-10-21 12:32 ` [PATCH 13/21] leds: aat1290: Prevent out-of-bounds read in aat1290_brightness_to_intensity() Lee Jones
2026-10-21 12:32 ` [PATCH 14/21] leds: flash: Avoid divide-by-zero in led_clamp_align() Lee Jones
2026-10-21 12:32 ` [PATCH 15/21] leds: lm3532: Validate LED string indices in lm3532_parse_node() Lee Jones
2026-10-21 12:32 ` [PATCH 16/21] leds: lm3532: Clamp full-scale current to minimum bound Lee Jones
2026-10-21 12:32 ` [PATCH 17/21] leds: aat1290: Avoid leaking devres pinctrl handles on strobe source changes Lee Jones
2026-10-21 12:32 ` [PATCH 18/21] leds: aw2013: Unlock chip mutex before registering LEDs Lee Jones
2026-10-21 12:32 ` [PATCH 19/21] leds: is31fl32xx: Clamp channel current limit in is31fl3293_reset() Lee Jones
2026-10-21 12:32 ` [PATCH 20/21] leds: flash: Terminate sysfs_groups array with NULL Lee Jones
2026-10-21 12:32 ` [PATCH 21/21] leds: lm3692x: Use devm_mutex_init() to avoid premature mutex destruction Lee Jones
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=20261021123406.3163547-1-lee@kernel.org \
--to=lee@kernel.org \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=ben.whitten@gmail.com \
--cc=christian.hitz@bbv.ch \
--cc=cooloney@gmail.com \
--cc=daniel@zonque.org \
--cc=davem@davemloft.net \
--cc=dmantipov@yandex.ru \
--cc=dmurphy@ti.com \
--cc=drivshin@allworx.com \
--cc=eajames@linux.ibm.com \
--cc=ffainelli@freebox.fr \
--cc=j.anaszewski@samsung.com \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=lenz@cs.wisc.edu \
--cc=lhenriques@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=luca@lucaweiss.eu \
--cc=ncase@xes-inc.com \
--cc=nikitos.tr@gmail.com \
--cc=oliver@opencloud.com \
--cc=pavel@kernel.org \
--cc=rpurdie@openedhand.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®