mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Maxime Ripard" <mripard@kernel.org>
To: "Sebastian Wick" <sebastian.wick@redhat.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	"David Airlie" <airlied@gmail.com>,
	"Haneen Mohammed" <hamohammed.sa@gmail.com>,
	"Louis Chauvet" <louis.chauvet@bootlin.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Melissa Wen" <melissa.srw@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Thomas Zimmermann" <tzimmermann@suse.de>
Subject: Re: [PATCH 2/2] drm/vkms: Use drm_dev_unplug() for ConfigFS device removal
Date: Thu, 05 Nov 2026 15:56:54 +0000	[thread overview]
Message-ID: <654ec450bfe86c60279a352014ead93c@kernel.org> (raw)
In-Reply-To: <20261031225901.3200167-2-sebastian.wick@redhat.com>

On Sat, 31 Oct 2026 23:58:59 +0100, Sebastian Wick wrote:
> VKMS ConfigFS devices can be disabled while userspace still holds open
> file descriptors. Using drm_dev_unregister() leaves the device in a
> state where ioctls are still accepted but internal locks can contend
> with the teardown path. Specifically, drmModeGetConnector() triggers
> fill_modes which acquires mode_config locks that contend with
> 
> [ ... ]

Acked-by: Maxime Ripard <mripard@kernel.org>

Thanks!
Maxime

  reply	other threads:[~2026-11-05 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-31 22:58 [PATCH 1/2] drm/vkms: Add drm_dev_enter/exit guards for hot-removable paths Sebastian Wick
2026-10-31 22:58 ` [PATCH 2/2] drm/vkms: Use drm_dev_unplug() for ConfigFS device removal Sebastian Wick
2026-11-05 15:56   ` Maxime Ripard [this message]
2026-11-05 18:36   ` Oarora Etimis
2026-11-05 18:36 ` [PATCH 1/2] drm/vkms: Add drm_dev_enter/exit guards for hot-removable paths Oarora Etimis

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=654ec450bfe86c60279a352014ead93c@kernel.org \
    --to=mripard@kernel.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hamohammed.sa@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=louis.chauvet@bootlin.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=melissa.srw@gmail.com \
    --cc=sebastian.wick@redhat.com \
    --cc=simona@ffwll.ch \
    --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
all inboxes | Powered by JetHome®