From: Boris Brezillon <boris.brezillon@collabora.com>
To: Chia-I Wu <olvaffe@gmail.com>
Cc: "Steven Price" <steven.price@arm.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] drm: Define a conditional guard for drm_dev_{enter,exit}()
Date: Mon, 18 May 2026 10:28:13 +0200 [thread overview]
Message-ID: <20260518102813.50555650@fedora> (raw)
In-Reply-To: <CAPaKu7TULU6_-8eoygq0svBTbnX-vFvF3sH5hDzyi9kDP-9enQ@mail.gmail.com>
On Thu, 14 May 2026 11:34:52 -0700
Chia-I Wu <olvaffe@gmail.com> wrote:
> On Wed, May 13, 2026 at 10:24 AM Boris Brezillon
> <boris.brezillon@collabora.com> wrote:
> >
> > Define a conditional drm_dev_access guard to automate the
> > drm_dev_{enter,exit}() sequence.
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> > ---
> > include/drm/drm_drv.h | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/include/drm/drm_drv.h b/include/drm/drm_drv.h
> > index 42fc085f986d..79d1958f93e4 100644
> > --- a/include/drm/drm_drv.h
> > +++ b/include/drm/drm_drv.h
> > @@ -490,6 +490,15 @@ void drm_dev_unplug(struct drm_device *dev);
> > int drm_dev_wedged_event(struct drm_device *dev, unsigned long method,
> > struct drm_wedge_task_info *info);
> >
> > +/*
> > + * Only the conditional drm_dev_access guard is valid. The drm_dev one is
> > + * here so we can extend it with a conditional variant.
> > + */
> > +DEFINE_LOCK_GUARD_1(drm_dev, struct drm_device,
> > + { WARN_ON("Use cond guards"); _T->idx = -1; },
> > + drm_dev_exit(_T->idx), int idx);
> If this is ever mis-used, drm_dev_exit(-1) seems to cause OOB access.
> Is BUG more appropriate than WARN_ON?
I actually had
if (_T->idx >= 0) drm_dev_exit(_T->idx),
at some point, and I ditched it thinking the WARN_ON_ONCE()
in srcu_read_unlock() would cover for that. I can add it back, of
course.
I'd be fine with a BUG_ON() too, but every time I tried to add one I've
been encouraged to handle the unexpected case instead.
Ideally, we would have a DEFINE_LOCK_GUARD_COND() variant that, instead
of expanding a non-conditional one, would define the whole thing so
that the non-conditional variant is never exposed.
>
> > +DEFINE_LOCK_GUARD_1_COND(drm_dev, _access, drm_dev_enter(_T->lock, &_T->idx));
> > +
> > /**
> > * drm_dev_is_unplugged - is a DRM device unplugged
> > * @dev: DRM device
> >
> > --
> > 2.54.0
> >
next prev parent reply other threads:[~2026-05-18 8:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 16:58 [PATCH 0/6] drm/panthor: Use guards Boris Brezillon
2026-05-13 16:58 ` [PATCH 1/6] drm/panthor: Driver-wide xxx_[un]lock -> [scoped_]guard replacement Boris Brezillon
2026-05-14 13:16 ` Steven Price
2026-05-14 17:09 ` Chia-I Wu
2026-05-18 8:43 ` Boris Brezillon
2026-05-18 8:57 ` Boris Brezillon
2026-05-18 23:50 ` [Linaro-mm-sig] " Chia-I Wu
2026-05-13 16:58 ` [PATCH 2/6] dma-resv: Define guards for context-less dma_resv locks Boris Brezillon
2026-05-14 18:23 ` Chia-I Wu
2026-05-18 7:10 ` Christian König
2026-05-18 9:14 ` Boris Brezillon
2026-05-18 12:18 ` Christian König
2026-05-18 14:15 ` Boris Brezillon
2026-05-13 16:58 ` [PATCH 3/6] drm: Define a conditional guard for drm_dev_{enter,exit}() Boris Brezillon
2026-05-14 18:34 ` Chia-I Wu
2026-05-18 8:28 ` Boris Brezillon [this message]
2026-05-18 9:16 ` Christian König
2026-05-18 9:35 ` Boris Brezillon
2026-05-13 16:58 ` [PATCH 4/6] drm/panthor: Use guards for resv locking Boris Brezillon
2026-05-14 18:35 ` Chia-I Wu
2026-05-13 16:58 ` [PATCH 5/6] drm/panthor: Use the drm_dev_access guard Boris Brezillon
2026-05-14 18:36 ` Chia-I Wu
2026-05-13 16:58 ` [PATCH 6/6] drm/panthor: Add a new guard for our custom resume_and_get() PM helper Boris Brezillon
2026-05-14 18:39 ` Chia-I Wu
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=20260518102813.50555650@fedora \
--to=boris.brezillon@collabora.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.com \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--cc=sumit.semwal@linaro.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