From: Lee Jones <lee@kernel.org>
To: Pavel Machek <pavel@ucw.cz>, Hans de Goede <hdegoede@redhat.com>
Cc: "Jakub Kicinski" <kuba@kernel.org>,
"Andrew Lunn" <andrew@lunn.ch>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
regressions@lists.linux.dev, linux-leds@vger.kernel.org,
"Genes Lists" <lists@sapience.com>,
"Johannes Wüller" <johanneswueller@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] leds: class: Revert: "If no default trigger is given, make hw_control trigger the default trigger"
Date: Thu, 20 Jun 2024 10:49:29 +0100 [thread overview]
Message-ID: <20240620094929.GK3029315@google.com> (raw)
In-Reply-To: <171887679701.1126294.11039062848140573919.b4-ty@kernel.org>
On Thu, 20 Jun 2024, Lee Jones wrote:
> On Fri, 07 Jun 2024 12:18:47 +0200, Hans de Goede wrote:
> > Commit 66601a29bb23 ("leds: class: If no default trigger is given, make
> > hw_control trigger the default trigger") causes ledtrig-netdev to get
> > set as default trigger on various network LEDs.
> >
> > This causes users to hit a pre-existing AB-BA deadlock issue in
> > ledtrig-netdev between the LED-trigger locks and the rtnl mutex,
> > resulting in hung tasks in kernels >= 6.9.
> >
> > [...]
>
> Applied, thanks!
>
> [1/1] leds: class: Revert: "If no default trigger is given, make hw_control trigger the default trigger"
> commit: 3acc45f2ceb0609812522e45aec4cb9516e1c586
Cancel.
It looks as though Linus did end up picking this up, just silently.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2024-06-20 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 10:18 [PATCH] leds: class: Revert: "If no default trigger is given, make hw_control trigger the default trigger" Hans de Goede
2024-06-07 12:03 ` Andrew Lunn
2024-06-07 15:26 ` Hans de Goede
2024-06-12 14:58 ` Linux regression tracking (Thorsten Leemhuis)
2024-06-12 15:06 ` Hans de Goede
2024-06-12 15:26 ` Lee Jones
2024-06-13 6:01 ` Linux regression tracking (Thorsten Leemhuis)
2024-06-16 11:40 ` Thorsten Leemhuis
2024-06-20 9:46 ` Lee Jones
2024-06-20 9:49 ` 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=20240620094929.GK3029315@google.com \
--to=lee@kernel.org \
--cc=andrew@lunn.ch \
--cc=hdegoede@redhat.com \
--cc=hkallweit1@gmail.com \
--cc=johanneswueller@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=lists@sapience.com \
--cc=pavel@ucw.cz \
--cc=regressions@lists.linux.dev \
--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 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.