linux-kernel - Re: [PATCH] nvmem: core: Check read_only flag for force_ro in bin_attr_nvmem

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

Message-ID: <c181a856-164b-41cf-b512-b8dba3247ae3@denx.de>
Date: Wed, 25 Sep 2024 00:42:04 +0200
From: Marek Vasut <marex@...x.de>
To: linux-i2c@...r.kernel.org
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nvmem: core: Check read_only flag for force_ro in
 bin_attr_nvmem_write()

On 7/13/24 5:39 PM, Marek Vasut wrote:
> The bin_attr_nvmem_write() must check the read_only flag and block
> writes on read-only devices, now that a nvmem device can be switched
> between read-write and read-only mode at runtime using the force_ro
> attribute. Add the missing check.
> 
> Fixes: 9d7eb234ac7a ("nvmem: core: Implement force_ro sysfs attribute")
> Signed-off-by: Marek Vasut <marex@...x.de>
> ---
> Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
> Cc: linux-kernel@...r.kernel.org
It seems this bugfix is not even in next, any news ?