linux-kernel - Re: [PATCH] power: supply: max77705: 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 for Android: free password hash cracker in your pocket

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

Message-Id: <176213091324.301408.11975062916698702054.b4-ty@collabora.com>
Date: Mon, 03 Nov 2025 01:48:33 +0100
From: Sebastian Reichel <sebastian.reichel@...labora.com>
To: Sebastian Reichel <sre@...nel.org>, 
 Dzmitry Sankouski <dsankouski@...il.com>, Lee Jones <lee@...nel.org>, 
 linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: stable@...r.kernel.org
Subject: Re: [PATCH] power: supply: max77705: Fix potential IRQ chip
 conflict when probing two devices


On Thu, 23 Oct 2025 12:29:06 +0200, Krzysztof Kozlowski wrote:
> MAX77705 charger 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 max77705_charger_data').  devm_regmap_add_irq_chip()
> does not make a copy of 'struct regmap_irq_chip' but stores the pointer.
> 
> [...]

Applied, thanks!

[1/1] power: supply: max77705: Fix potential IRQ chip conflict when probing two devices
      commit: 1cb053ea2e1dedd8f2d9653b7c3ca5b93c8c9275

Best regards,
-- 
Sebastian Reichel <sebastian.reichel@...labora.com>