linux-kernel - Re: [PATCH v2 1/3] i2c: rcar: bring hardware to known state when probing

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

Message-ID: <d6i3ojzbthieq52teugiuxdxjp2la6cjtsleq4esbfgup6cgqf@obfadtyrdpuh>
Date: Tue, 9 Jul 2024 01:19:49 +0200
From: Andi Shyti <andi.shyti@...nel.org>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: linux-renesas-soc@...r.kernel.org, 
	Dirk Behme <dirk.behme@...bosch.com>, Geert Uytterhoeven <geert+renesas@...der.be>, 
	Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>, linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/3] i2c: rcar: bring hardware to known state when
 probing

Hi Wolfram,

On Sun, Jul 07, 2024 at 10:28:46AM GMT, Wolfram Sang wrote:
> When probing, the hardware is not brought into a known state. This may
> be a problem when a hypervisor restarts Linux without resetting the
> hardware, leaving an old state running. Make sure the hardware gets
> initialized, especially interrupts should be cleared and disabled.
> 
> Reported-by: Dirk Behme <dirk.behme@...bosch.com>
> Reported-by: Geert Uytterhoeven <geert+renesas@...der.be>
> Closes: https://lore.kernel.org/r/20240702045535.2000393-1-dirk.behme@de.bosch.com
> Fixes: 6ccbe607132b ("i2c: add Renesas R-Car I2C driver")
> Signed-off-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
> ---
> 
> Should go to for-current.

merged in i2c/i2c-host-fixes.

Thanks,
Andi