linux-kernel - Re: [PATCH v3] nvmem: rmem: Fix return value of rmem

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 for Android: free password hash cracker in your pocket

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

Date: Tue, 11 Jun 2024 10:30:06 +0100
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
 Rob Herring <robh@...nel.org>, Nicolas Saenz Julienne <nsaenz@...nel.org>, 
 Dan Carpenter <dan.carpenter@...aro.org>, 
 Joy Chakraborty <joychakr@...gle.com>
Cc: linux-kernel@...r.kernel.org, manugautam@...gle.com, 
 stable@...r.kernel.org
Subject: Re: [PATCH v3] nvmem: rmem: Fix return value of rmem_read()


On Fri, 07 Jun 2024 16:05:10 +0000, Joy Chakraborty wrote:
> reg_read() callback registered with nvmem core expects 0 on success and
> a negative value on error but rmem_read() returns the number of bytes
> read which is treated as an error at the nvmem core.
> 
> This does not break when rmem is accessed using sysfs via
> bin_attr_nvmem_read()/write() but causes an error when accessed from
> places like nvmem_access_with_keepouts(), etc.
> 
> [...]

Applied, thanks!

[1/1] nvmem: rmem: Fix return value of rmem_read()
      commit: 139eb4bb33a2857fe439c02a201a85af52ce6186

Best regards,
-- 
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>