linux-kernel - Re: (subset) [RFT PATCH] mfd: max77620: Fix potential IRQ chip conflict when probing two devices

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: <176243507327.1833794.15963365133999992020.b4-ty@kernel.org>
Date: Thu, 06 Nov 2025 13:17:53 +0000
From: Lee Jones <lee@...nel.org>
To: Lee Jones <lee@...nel.org>, Laxman Dewangan <ldewangan@...dia.com>, 
 linux-kernel@...r.kernel.org, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: stable@...r.kernel.org
Subject: Re: (subset) [RFT PATCH] mfd: max77620: Fix potential IRQ chip
 conflict when probing two devices

On Thu, 23 Oct 2025 12:19:40 +0200, Krzysztof Kozlowski wrote:
> MAX77620 is most likely always a single device on the board, however
> nothing stops board designers to have two of them, thus same device
> driver could probe twice. Or user could manually try to probing second
> time.
> 
> Device driver is not ready for that case, because it allocates
> statically 'struct regmap_irq_chip' as non-const and stores during
> probe in 'irq_drv_data' member a pointer to per-probe state
> container ('struct max77620_chip').  devm_regmap_add_irq_chip() does not
> make a copy of 'struct regmap_irq_chip' but store the pointer.
> 
> [...]

Applied, thanks!

[1/1] mfd: max77620: Fix potential IRQ chip conflict when probing two devices
      commit: a65059b3e91b811aff2ccfd53578e06384779ef7

--
Lee Jones [李琼斯]