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]
Message-ID: <bf19c4f4-5ed5-4210-b123-92f79d27d6e7@web.de>
Date: Tue, 18 Mar 2025 13:03:23 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Miquel Raynal <miquel.raynal@...tlin.com>, linux-mtd@...ts.infradead.org
Cc: kernel-janitors@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
 cocci@...ia.fr, Richard Weinberger <richard@....at>,
 Vignesh Raghavendra <vigneshr@...com>
Subject: Re: mtd: cfi_cmdset_0001: Fix exception handling in
 cfi_intelext_setup()

>> The label “setup_err” was used to jump to another pointer check despite of
>> the detail in the implementation of the function “cfi_intelext_setup”
>> that it was determined already that a corresponding variable contained
>> a null pointer because of a failed memory allocation.
>
> Can you please rephrase the commit log? It is super hard to understand.
Which wording variant would you find nicer for provided information?

* used jump targets

* null pointer assignments


Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ