From: Sebastian Siewior <bigeasy@linutronix.de>
To: Jiri Kosina <jikos@kernel.org>
Cc: John Ogness <john.ogness@linutronix.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: fb-helper: Avoid nesting spinlock_t into raw_spinlock_t
Date: Wed, 16 Feb 2022 08:40:45 +0100 [thread overview]
Message-ID: <YgyqfQkz+/Xs7VWR@linutronix.de> (raw)
In-Reply-To: <nycvar.YFH.7.76.2202152058300.11721@cbobk.fhfr.pm>
On 2022-02-15 20:59:24 [+0100], Jiri Kosina wrote:
> Thanks for confirmation, seems like this problem is indeed cured by your
> series.
Oki.
> I still believe though that we shouldn't let 5.17 released with this
> warning being emitted into dmesg, so I'd suggest going with my patch for
> mainline, and revert it in your series on top of it.
No. That warning is only visible with CONFIG_PROVE_RAW_LOCK_NESTING with
the following paragraph in its help:
| NOTE: There are known nesting problems. So if you enable this
| option expect lockdep splats until these problems have been fully
| addressed which is work in progress. This config switch allows to
| identify and analyze these problems. It will be removed and the
| check permanently enabled once the main issues have been fixed.
This warning in this call chain should affect every console driver which
acquires a lock.
> Thanks,
Sebastian
prev parent reply other threads:[~2022-02-16 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 15:43 [PATCH] drm: fb-helper: Avoid nesting spinlock_t into raw_spinlock_t Jiri Kosina
2022-02-15 15:49 ` Sebastian Siewior
2022-02-15 16:23 ` John Ogness
2022-02-15 19:59 ` Jiri Kosina
2022-02-16 7:40 ` Sebastian Siewior [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=YgyqfQkz+/Xs7VWR@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jikos@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).