linux-kernel - Re: [PATCH] drm/sharp-memory: Fix IS_ERR() vs NULL check in sharp_memory

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: <7bfb2092-27da-4368-b95c-a57c11127651@web.de>
Date: Sat, 31 Jan 2026 08:04:38 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Chen Ni <nichen@...as.ac.cn>, dri-devel@...ts.freedesktop.org,
 Alex Lanzano <lanzano.alex@...il.com>, David Airlie <airlied@...il.com>,
 Dmitry Baryshkov <lumag@...nel.org>,
 Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
 Maxime Ripard <mripard@...nel.org>, Mehdi Djait <mehdi.djait@...tlin.com>,
 Simona Vetter <simona@...ll.ch>, Thomas Zimmermann <tzimmermann@...e.de>,
 Uwe Kleine-König <u.kleine-koenig@...libre.com>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm/sharp-memory: Fix IS_ERR() vs NULL check in
 sharp_memory_probe()

…
> Replace the NULL check after devm_drm_dev_alloc() with IS_ERR()

May extra error messages be omitted for selected allocation failures?



>                                                                 and add
> a missing IS_ERR() check after devm_gpiod_get_optional(). On error,
> return the error code from the probe function to ensure proper failure
> handling rather than proceeding with invalid pointers.

* Were any source code analysis tools involved here?

* Did anything hinder to add any tags (like “Fixes” and “Cc”) accordingly?


Regards,
Markus