From: Pavel Machek <pavel@ucw.cz>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>, Dan Murphy <dmurphy@ti.com>,
linux-ide@vger.kernel.org, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: 5.11 new lockdep warning related to led-class code (also may involve ata / piix controller)
Date: Tue, 2 Feb 2021 10:32:29 +0100 [thread overview]
Message-ID: <20210202093228.GA29131@amd> (raw)
In-Reply-To: <cc1cac99-e3de-9585-bfa0-db7b013e8a80@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
Hi!
> > Is it a regression? AFAIK it is a bug that has been there
> > forever... My original plan was to simply wait for 5.12, so it gets
> > full release of testing...
>
> It may have been a pre-existing bug which got triggered by libata
> changes?
Fixes tag suggests it is rather old.
> I don't know. I almost always run all my locally build kernels with lockdep
> enabled and as the maintainer of the vboxvideo, vboxguest and vboxsf guest
> drivers in the mainline kernel I quite often boot local build kernels inside
> a vm.
>
> So I believe that lockdep tripping over this is new in 5.11, which is why
> I called it a regression.
>
> And the fix seems very safe and simple, so IMHO it would be good to get
> this into 5.11
It is in 5.11 now, and also -stable kernels. (Which suprised me a
bit).
Testing would be welcome.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2021-02-02 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 21:18 5.11 new lockdep warning related to led-class code (also may involve ata / piix controller) Hans de Goede
2021-01-12 22:30 ` Pavel Machek
2021-01-13 8:59 ` Hans de Goede
2021-01-25 13:15 ` Hans de Goede
2021-01-27 22:01 ` Pavel Machek
2021-01-28 13:02 ` Hans de Goede
2021-02-02 9:32 ` Pavel Machek [this message]
2021-02-02 10:33 ` Hans de Goede
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=20210202093228.GA29131@amd \
--to=pavel@ucw.cz \
--cc=axboe@kernel.dk \
--cc=dmurphy@ti.com \
--cc=hdegoede@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@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.