linux-kernel - Re: [v2] drm/amdkfd: fix a memory leak in device_queue_manager

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <f1c4457a-14d1-4b99-95f8-da23968d59f6@web.de>
Date: Sat, 10 Jan 2026 08:20:27 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Felix Kühling <felix.kuehling@....com>,
 Haoxiang Li <lihaoxiang@...c.iscas.ac.cn>, amd-gfx@...ts.freedesktop.org,
 dri-devel@...ts.freedesktop.org, Alex Deucher <alexander.deucher@....com>,
 Christian König <christian.koenig@....com>,
 David Airlie <airlied@...il.com>, Oak Zeng <ozeng@....com>,
 Simona Vetter <simona@...ll.ch>
Cc: stable@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [v2] drm/amdkfd: fix a memory leak in device_queue_manager_init()

>>> But it's also harmless.
>> How do you think about to avoid special development concerns here?
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?h=v6.19-rc4#n1242
> 
> No. I think the WARN is used exactly as it was meant to be here: to check for something that should never happen.

Do we stumble on another target conflict at such a source code place?

Would you like to avoid undefined behaviour here?
https://wiki.sei.cmu.edu/confluence/spaces/c/pages/87152449/EXP34-C.+Do+not+dereference+null+pointers

Regards,
Markus