From: Bert Karwatzki <spasswolf@web.de>
To: linux-kernel@vger.kernel.org, Rafal Ostrowski <rafal.ostrowski@amd.com>
Cc: linux-next@vger.kernel.org, linux-rt-devel@lists.linux.dev,
amd-gfx@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
spasswolf@web.de
Subject: Re: [Re] kernel panic during shutdown in v7.1+ with PREEMPT_RT
Date: Mon, 27 Jul 2026 12:06:55 +0200 [thread overview]
Message-ID: <5b5559e0fcc162bb0a2b7ab9764b8040c981c1d5.camel@web.de> (raw)
In-Reply-To: <f012ef660c71e5d85bd746caab2f6a6e456671de.camel@web.de>
This can be fixed like this
struct dc_plane_state *dc_create_plane_state(const struct dc *dc)
{
struct dc_plane_state *plane_state;
DC_RUN_WITH_PREEMPTION_ENABLED(plane_state = kvzalloc_obj(*plane_state, GFP_ATOMIC));
if (NULL == plane_state)
return NULL;
kref_init(&plane_state->refcount);
dc_plane_construct(dc->ctx, plane_state);
return plane_state;
}
I also found missing DC_RUN_WITH_PREEMPTION_ENABLED in an error path, I'm preparing
a patch for next-20260721 (next-20260722+ have broken reboot due to the mt7925 issue
mentioned above).
Also, is preempt_{disable,enable}() really necessary in DC_FPU_{BEGIN,END}?
Could migrate_{disable,enable}() be enough instead? This way we wouldn't need
DC_RUN_WITH_PREEMPTION_ENABLED at all(?).
Bert Karwatzki
next prev parent reply other threads:[~2026-07-27 10:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 12:34 kernel panic during shutdown in v7.2-rc4 and next-20260722 " Bert Karwatzki
2026-07-23 12:43 ` [Re] " Bert Karwatzki
2026-07-23 13:10 ` [Re] kernel panic during shutdown in v7.2-rc{3,4} " Bert Karwatzki
2026-07-23 13:23 ` Bert Karwatzki
2026-07-23 16:17 ` Bert Karwatzki
2026-07-23 22:51 ` [Re] kernel panic during shutdown in next-20260722 Bert Karwatzki
2026-07-24 15:08 ` Bert Karwatzki
2026-07-25 19:58 ` Bert Karwatzki
2026-07-25 23:16 ` Bert Karwatzki
2026-07-26 18:47 ` Bert Karwatzki
2026-07-26 22:52 ` Bert Karwatzki
2026-07-27 10:06 ` Bert Karwatzki [this message]
2026-07-27 10:35 ` [Re] kernel panic during shutdown in v7.1+ with PREEMPT_RT Ostrowski, Rafal
2026-07-27 10:50 ` [PATCH] drm/amd/display: fix usage of DC_FPU_{BEGIN,END} " Bert Karwatzki
2026-07-27 11:11 ` sashiko-bot
2026-07-28 0:51 ` mikhail.v.gavrilov
2026-07-29 12:35 ` Bert Karwatzki
2026-07-29 14:39 ` Mikhail Gavrilov
2026-07-29 17:46 ` Bert Karwatzki
2026-08-01 7:17 ` Bert Karwatzki
2026-08-01 7:35 ` sashiko-bot
2026-08-01 10:17 ` Mikhail Gavrilov
2026-08-07 12:58 ` Bert Karwatzki
2026-08-07 13:31 ` sashiko-bot
2026-08-06 3:47 ` kernel test robot
2026-08-06 4:29 ` kernel test robot
2026-08-07 12:49 ` [PATCH v7.2-rc6] " Bert Karwatzki
2026-08-07 13:13 ` sashiko-bot
2026-08-07 14:00 ` Greg KH
2026-08-27 12:49 ` Sebastian Andrzej Siewior
2026-08-27 21:07 ` Bert Karwatzki
2026-08-28 9:55 ` Sebastian Andrzej Siewior
2026-09-01 14:01 ` Bert Karwatzki
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=5b5559e0fcc162bb0a2b7ab9764b8040c981c1d5.camel@web.de \
--to=spasswolf@web.de \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=mario.limonciello@amd.com \
--cc=rafal.ostrowski@amd.com \
--cc=tglx@linutronix.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®