linux-kernel - Re: [PATCH] clk: microchip: check for null return of devm

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] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 21 Nov 2022 15:26:44 +0800
From:   Hui Tang <tanghui20@...wei.com>
To:     Conor Dooley <conor@...nel.org>
CC:     <mturquette@...libre.com>, <sboyd@...nel.org>,
        <linux-clk@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <yusongping@...wei.com>, <claudiu.beznea@...rochip.com>,
        <conor.dooley@...rochip.com>
Subject: Re: [PATCH] clk: microchip: check for null return of devm_kzalloc()



On 2022/11/19 18:43, Conor Dooley wrote:
> On Sat, Nov 19, 2022 at 01:48:58PM +0800, Hui Tang wrote:
>> Because of the possilble failure of devm_kzalloc(), name might be NULL and
>> will cause null pointer derefrence later.
>
> In theory, yeah?
>
> (note to self, s/refrence/reference/, s/possilble/possible)

Sorry, I make spelling mistakes.

Thanks.