linux-kernel - Re: [PATCH v3] eeprom: at24: fix memory corruption race condition

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: <939095cb-b9c0-4214-9429-7b45f9a31f36@web.de>
Date: Sat, 20 Apr 2024 11:11:05 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Daniel Okazaki <dtokazaki@...gle.com>, kernel-team@...roid.com,
 linux-i2c@...r.kernel.org, kernel-janitors@...r.kernel.org,
 Arnd Bergmann <arnd@...db.de>, Bartosz Golaszewski <brgl@...ev.pl>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] eeprom: at24: fix memory corruption race condition

> If the eeprom is not accessible, an nvmem device will be registered, the
> read will fail, and the device will be torn down.
…

Can it be nicer to present the introduction for failure conditions as an enumeration?

> Move the failure point before registering the nvmem device.
…

I would interpret the diff data more in the way that a devm_nvmem_register() call
should be performed a bit later in the implementation of the function “at24_probe”.
How do you think about to mention the affected function also in the summary phrase?

> ---
…

Please add a version description for your change approach.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9-rc4#n713

Regards,
Markus