All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: Krzysztof Niemiec <krzysztof.niemiec@intel.com>,
	<dri-devel@lists.freedesktop.org>,
	<intel-gfx@lists.freedesktop.org>
Cc: Krzysztof Karas <krzysztof.karas@intel.com>,
	Simona Vetter <simona@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	David Airlie <airlied@gmail.com>,
	Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
	Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>,
	Andi Shyti <andi.shyti@linux.intel.com>
Subject: Re: [PATCH v2 0/2] DRM device registration fixes
Date: Thu, 16 Jul 2026 15:07:22 +0200	[thread overview]
Message-ID: <DK00OJM95532.WUNTR7EC2NFK@intel.com> (raw)
In-Reply-To: <20260716120018.20406-2-krzysztof.niemiec@intel.com>

Hi Krzysztof,

On Thu Jul 16, 2026 at 2:00 PM CEST, Krzysztof Niemiec wrote:
> This series contains patches pertaining the drm_dev_register() and
> drm_dev_unregister() functions. Turns out drm_dev_register() doesn't
> properly unwind its effects in the error path, causing confusion and
> bugs.
>
> Additionally, a related patch for i915 is bundled, as i915 mistakenly
> calls drm_dev_unregister() in the error path triggered by failing
> drm_dev_register(), which on one hand introduced a WARN_ON() in
> drm_client_sysrq_unregister(), caused by calling it without a previous
> _register() (as it was skipped in drm_dev_register()); but on the other
> hand silenced yet another WARN_ON() later on in the error path in
> drm_mode_config_cleanup(). With the other patch, the driver can just
> handle the error from drm_dev_register() cleanly without calling
> drm_dev_unregister(). This is explained in detail in both the patches.
As has been said, you could reorder the patches. Other than that LGTM.
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>

-- 
Best regards,
Sebastian


      parent reply	other threads:[~2026-07-16 13:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16 12:00 [PATCH v2 0/2] DRM device registration fixes Krzysztof Niemiec
2026-07-16 12:00 ` [PATCH v2 1/2] drm/i915: Remove drm_dev_unregister() from the error path during i915_driver_register() Krzysztof Niemiec
2026-07-16 12:00 ` [PATCH v2 2/2] drm: Unwind drm device registration upon error Krzysztof Niemiec
2026-07-16 12:47 ` ✗ i915.CI.BAT: failure for DRM device registration fixes Patchwork
2026-07-16 13:07 ` Sebastian Brzezinka [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=DK00OJM95532.WUNTR7EC2NFK@intel.com \
    --to=sebastian.brzezinka@intel.com \
    --cc=airlied@gmail.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=janusz.krzysztofik@linux.intel.com \
    --cc=krzysztof.karas@intel.com \
    --cc=krzysztof.niemiec@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=simona@ffwll.ch \
    /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.