From: Sasha Levin <sashal@kernel.org>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Ryosuke Yasuoka <ryasuoka@redhat.com>,
David Airlie <airlied@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
Chia-I Wu <olvaffe@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Simona Vetter <simona@ffwll.ch>,
Dmitry Baryshkov <lumag@kernel.org>,
Javier Martinez Canillas <javierm@redhat.com>,
dri-devel@lists.freedesktop.org, virtualization@lists.linux.dev,
linux-kernel@vger.kernel.org,
Mikko Rapeli <mikko.rapeli@linaro.org>
Subject: Re: [PATCH v2] drm/virtio: fix deadlock in display_info_cb by removing hotplug from dequeue worker
Date: Fri, 24 Jul 2026 07:22:36 -0400 [thread overview]
Message-ID: <20260724105500.stable-0004@kernel.org> (raw)
In-Reply-To: <amG_T7Kb7DW3VTxm@nuoska>
> In Yocto distro, this change released in v7.2-rc4 seems to fix quite severe qemu
> boot hangs seen with 6.18 stable kernels. Details in
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=16217
>
> Please apply this to to 6.18 and other stable trees.
Queued for 6.6, 6.12, 6.18, and 7.1, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-24 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 13:01 [PATCH v2] drm/virtio: fix deadlock in display_info_cb by removing hotplug from dequeue worker Ryosuke Yasuoka
2026-07-13 16:31 ` Dmitry Osipenko
2026-07-23 7:14 ` Mikko Rapeli
2026-07-23 18:56 ` Dmitry Osipenko
2026-07-24 11:22 ` Sasha Levin [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=20260724105500.stable-0004@kernel.org \
--to=sashal@kernel.org \
--cc=airlied@redhat.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=javierm@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mikko.rapeli@linaro.org \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.com \
--cc=ryasuoka@redhat.com \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
/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