linux-kernel - Re: [PATCH v2] nvmem: zynqmp_nvmem: unbreak driver after cleanup

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

Message-Id: <174595725468.31828.5794331995738765114.b4-ty@kernel.org>
Date: Tue, 29 Apr 2025 21:07:34 +0100
From: Srinivas Kandagatla <srini@...nel.org>
To: Praveen Teja Kundanala <praveen.teja.kundanala@....com>, 
 Kalyani Akula <kalyani.akula@....com>, Michal Simek <michal.simek@....com>, 
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
 Peter Korsgaard <peter@...sgaard.com>
Cc: stable@...r.kernel.org, Kalyani Akula <Kalyani.akula@....com>, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] nvmem: zynqmp_nvmem: unbreak driver after cleanup


On Tue, 22 Apr 2025 16:21:12 +0200, Peter Korsgaard wrote:
> Commit 29be47fcd6a0 ("nvmem: zynqmp_nvmem: zynqmp_nvmem_probe cleanup")
> changed the driver to expect the device pointer to be passed as the
> "context", but in nvmem the context parameter comes from nvmem_config.priv
> which is never set - Leading to null pointer exceptions when the device is
> accessed.
> 
> 
> [...]

Applied, thanks!

[1/1] nvmem: zynqmp_nvmem: unbreak driver after cleanup
      commit: c708bbd57d158d9f20c2fcea5bcb6e0afac77bef

Best regards,
-- 
Srinivas Kandagatla <srini@...nel.org>