public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
* linux-stable 6.1.53 kernel crash on COLOR_ID_MULTI handling change
@ 2023-09-13 18:57 Da Xue
  2023-09-14 10:21 ` Pavel Machek
  0 siblings, 1 reply; 3+ messages in thread
From: Da Xue @ 2023-09-13 18:57 UTC (permalink / raw)
  To: Pavel Machek, linux-leds, linux-kernel, linux-stable

Hi Pavel,

We have running systems that use COLOR_ID_MULTI. The GPIO toggles
between two colors and we have used the identifier. RGB is not a good
fit since it is not a RGB LED. Please provide guidance.

This patch causes the system to not start: f741121a2251 leds: Fix
BUG_ON check for LED_COLOR_ID_MULTI that is always false

It was also backported to stable causing previously booting systems to
no longer boot.

Best,
Da Xue

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-stable 6.1.53 kernel crash on COLOR_ID_MULTI handling change
  2023-09-13 18:57 linux-stable 6.1.53 kernel crash on COLOR_ID_MULTI handling change Da Xue
@ 2023-09-14 10:21 ` Pavel Machek
  2023-09-18 14:11   ` Marek Behún
  0 siblings, 1 reply; 3+ messages in thread
From: Pavel Machek @ 2023-09-14 10:21 UTC (permalink / raw)
  To: Da Xue, kabel, lee, sashal; +Cc: linux-leds, linux-kernel, linux-stable

[-- Attachment #1: Type: text/plain, Size: 631 bytes --]

Hi!

> We have running systems that use COLOR_ID_MULTI. The GPIO toggles
> between two colors and we have used the identifier. RGB is not a good
> fit since it is not a RGB LED. Please provide guidance.
> 
> This patch causes the system to not start: f741121a2251 leds: Fix
> BUG_ON check for LED_COLOR_ID_MULTI that is always false
> 
> It was also backported to stable causing previously booting systems to
> no longer boot.

Lets cc patch authors.

And please drop this from stable, it does not belong there.

Best regards,
								Pavel
-- 
People of Russia, stop Putin before his war on Ukraine escalates.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-stable 6.1.53 kernel crash on COLOR_ID_MULTI handling change
  2023-09-14 10:21 ` Pavel Machek
@ 2023-09-18 14:11   ` Marek Behún
  0 siblings, 0 replies; 3+ messages in thread
From: Marek Behún @ 2023-09-18 14:11 UTC (permalink / raw)
  To: Pavel Machek; +Cc: Da Xue, lee, sashal, linux-leds, linux-kernel, linux-stable

On Thu, 14 Sep 2023 12:21:09 +0200
Pavel Machek <pavel@ucw.cz> wrote:

> Hi!
> 
> > We have running systems that use COLOR_ID_MULTI. The GPIO toggles
> > between two colors and we have used the identifier. RGB is not a good
> > fit since it is not a RGB LED. Please provide guidance.
> > 
> > This patch causes the system to not start: f741121a2251 leds: Fix
> > BUG_ON check for LED_COLOR_ID_MULTI that is always false
> > 
> > It was also backported to stable causing previously booting systems to
> > no longer boot.  
> 
> Lets cc patch authors.
> 
> And please drop this from stable, it does not belong there.
> 
> Best regards,
> 								Pavel

The BUG_ON was a no-op since it was introduced. It's purpose was to
prevent people from using LED_COLOR_ID_MULTI since it was thought that
non-RGB LEDs are not yet completely agreed on, or something.

But since the BUG_ON was a no-op, someone started using
LED_COLOR_ID_MULTI without noticing that they should not. There are now
even some in-tree device-tree files using LED_COLOR_ID_MULTI.

My patch that fixes the BUG_ON uncovered this and caused a regression
for some people.

I think we have to drop the BUG_ON altoghether now.

I've sent a patch to linux-leds doing just that.

Sorry for the incovenience.

Marek

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-09-18 16:45 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-09-13 18:57 linux-stable 6.1.53 kernel crash on COLOR_ID_MULTI handling change Da Xue
2023-09-14 10:21 ` Pavel Machek
2023-09-18 14:11   ` Marek Behún

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox