From: "Viktor Jägersküpper" <viktor_jaegerskuepper@freenet.de>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de
Cc: dri-devel@lists.freedesktop.org, airlied@gmail.com,
broonie@kernel.org, daniels@collabora.com,
jani.nikula@linux.intel.com, miguel.ojeda.sandonis@gmail.com,
pekka.paalanen@collabora.com, simona@ffwll.ch,
penguin-kernel@i-love.sakura.ne.jp, tytso@mit.edu,
ville.syrjala@linux.intel.com, linux-kernel@vger.kernel.org,
"Leandro Ribeiro" <leandro.ribeiro@collabora.com>,
"Daniel Stone" <daniel@fooishbar.org>,
"Viktor Jägersküpper" <viktor_jaegerskuepper@freenet.de>
Subject: Re: [PATCH v2 1/1] drm: use drm_warn() in validate_blend_mode_for_alpha_formats()
Date: Thu, 27 Aug 2026 13:25:18 +0200 [thread overview]
Message-ID: <29aca774-e502-4e5b-8ebf-7319bc8df77c@freenet.de> (raw)
In-Reply-To: <CAPj87rPvh6cz1JmRjfev5VJWZHhZqwyPn_nA3x43q6_qVDf=Tw@mail.gmail.com>
On 8/14/26 15:42, Daniel Stone wrote:
> Hi Leandro,
>
> On Fri, 31 Jul 2026 at 16:43, Leandro Ribeiro
> <leandro.ribeiro@collabora.com> wrote:
>> Commit 860e748bddcc ("drm: ensure blend mode supported if pixel format
>> with alpha exposed") introduced a WARN() to let driver developers know
>> that a previously valid behavior should now be changed.
>>
>> But WARN() should not be used for that, as it's a kernel warning report
>> mechanism for conditions that are not expected to happen. It also
>> produces a stack trace. Instead, a simple warning-level log message
>> should have been used, as drivers were expected to trigger the
>> condition.
>>
>> This is causing problems for fuzzers, as they may stop when encountering
>> a "BUG:" or "WARNING:" in the logs.
>>
>> Replace WARN() with drm_warn() in this function, avoiding these issues.
>>
>> Fixes: 860e748bddcc ("drm: ensure blend mode supported if pixel format with alpha exposed")
>> Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com>
>
> Thanks, this is:
> Reviewed-by: Daniel Stone <daniels@collabora.com>
>
> I'll fix up the newline when applying.
Hi Maarten, Maxime and Thomas,
can you cherry-pick this fix for drm-misc-fixes and send a pull-request
to Dave and Simona before the end of this week? I think this should land
in rc1 because people are already complaining about the warnings and it
will take some time to fix all affected drivers. I'm not even sure if
those fixes can land in mainline after rc1.
If you don't have the time to do this or the other fixes in
drm-misc-fixes are not yet ready for mainline, I will ask Linus to pick
this fix directly.
Viktor
next prev parent reply other threads:[~2026-08-27 11:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 15:42 [PATCH v2 0/1] drm: use drm_warn() in validate_blend_mode_for_alpha_formats() Leandro Ribeiro
2026-07-31 15:42 ` [PATCH v2 1/1] " Leandro Ribeiro
2026-07-31 15:49 ` sashiko-bot
2026-08-06 13:14 ` Tetsuo Handa
2026-08-13 14:46 ` Tetsuo Handa
2026-08-14 13:44 ` Daniel Stone
2026-08-14 13:42 ` Daniel Stone
2026-08-27 11:25 ` Viktor Jägersküpper [this message]
2026-08-27 12:30 ` Maxime Ripard
2026-08-27 13:28 ` [PATCH 00/11] mm/cma: charge cma allocation to memcg using per area counters Maxime Ripard
-- strict thread matches above, loose matches on Subject: below --
2026-08-21 18:56 Eric Chanudet
2026-08-21 18:56 ` [PATCH 01/11] mm/cma: drop const for struct page on release API Eric Chanudet
2026-08-21 18:56 ` [PATCH 02/11] mm/cma: include linux/cma.h in cma.h Eric Chanudet
2026-08-21 18:56 ` [PATCH 03/11] cgroup: add memory_cma_accounting mount option Eric Chanudet
2026-08-24 7:02 ` Maxime Ripard
2026-08-24 22:03 ` Eric Chanudet
2026-08-21 18:56 ` [PATCH 04/11] memcg: add cma charge/uncharge functions for area counters Eric Chanudet
2026-08-21 18:56 ` [PATCH 05/11] mm/cma: charge cma allocation to memcg per " Eric Chanudet
2026-08-21 18:56 ` [PATCH 06/11] memcg: register per-area usage counters in cgroupfs Eric Chanudet
2026-08-21 18:56 ` [PATCH 07/11] selftests: cgroup: add cma configs for cgroup selftest suite Eric Chanudet
2026-08-21 18:57 ` [PATCH 08/11] selftests: cgroup: add memcg cma tests Eric Chanudet
2026-08-21 18:57 ` [PATCH 09/11] selftests: cgroup: add a vmtest script for memcg Eric Chanudet
2026-08-21 18:57 ` [PATCH 10/11] selftests: cgroup: add memcg hugetlb_cma tests Eric Chanudet
2026-08-21 18:57 ` [PATCH 11/11] selftests: cgroup: amend vmtest-memcg to run the hugetlb cma tests Eric Chanudet
2026-08-23 7:02 ` [PATCH 00/11] mm/cma: charge cma allocation to memcg using per area counters Mike Rapoport
2026-08-24 21:58 ` Eric Chanudet
2026-08-25 7:40 ` Michal Hocko
2026-08-24 8:58 ` Michal Hocko
2026-08-25 14:47 ` Eric Chanudet
2026-08-25 14:59 ` Michal Hocko
2026-08-25 18:33 ` Eric Chanudet
2026-08-25 19:19 ` Michal Hocko
2026-08-25 20:58 ` Eric Chanudet
2026-08-26 8:04 ` Michal Hocko
2026-08-26 20:31 ` Eric Chanudet
2026-08-27 14:03 ` Michal Hocko
2026-08-25 15:45 ` David Hildenbrand (Arm)
2026-08-25 16:26 ` Michal Hocko
2026-08-25 18:50 ` Eric Chanudet
2026-08-26 8:02 ` David Hildenbrand (Arm)
2026-08-26 20:15 ` Eric Chanudet
2026-08-24 13:18 ` Michal Koutný
2026-08-25 14:54 ` Eric Chanudet
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=29aca774-e502-4e5b-8ebf-7319bc8df77c@freenet.de \
--to=viktor_jaegerskuepper@freenet.de \
--cc=airlied@gmail.com \
--cc=broonie@kernel.org \
--cc=daniel@fooishbar.org \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=leandro.ribeiro@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mripard@kernel.org \
--cc=pekka.paalanen@collabora.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=simona@ffwll.ch \
--cc=tytso@mit.edu \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.com \
/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.