Re: [PATCH v2 1/1] drm: use drm_warn() in validate_blend_mode_for_alpha_formats()

Tetsuo Handa <[email protected]>
Newsgroups gmane.linux.kernel,gmane.comp.video.dri.devel
Message-ID <[email protected]>
Merge window will open shortly. Can we have this fix applied before
commit 860e748bddcc ("drm: ensure blend mode supported if pixel format
with alpha exposed") hits upstream?

On 2026/08/06 22:14, Tetsuo Handa wrote:
> Who is supposed to take this patch?
> 
> Since this problem is preventing syzbot from testing changes in linux-next
> kernels for more than three weeks, I expect this patch to be applied
> as soon as possible.
> 
> On 2026/08/01 0:42, Leandro Ribeiro 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 <[email protected]>
>> ---
>>  drivers/gpu/drm/drm_mode_config.c | 5 +++--
>>  1 file changed, 3 insertions(+), 2 deletions(-)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.