linux-kernel - Re: [PATCH V1 1/1] mmc: sdio: Export an API to reinit the SDIO card

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: <aH8n1RNBmorMq9X9@infradead.org>
Date: Mon, 21 Jul 2025 22:55:33 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Sayali Lokhande <quic_sayalil@...cinc.com>
Cc: ulf.hansson@...aro.org, wsa+renesas@...g-engineering.com,
	avri.altman@....com, adrian.hunter@...el.com,
	shawn.lin@...k-chips.com, linux-mmc@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH V1 1/1] mmc: sdio: Export an API to reinit the SDIO card

On Mon, Jul 21, 2025 at 03:13:28PM +0530, Sayali Lokhande wrote:
> Some SDIO client drivers, manage external power to the SDIO card.
> In such cases, the card may be power-cycled independently of the
> MMC core's runtime PM state.
> Currently, reinitialization of the SDIO card is tied to the runtime
> PM resume path. However, if the card is powered off and on again before
> the autosuspend delay expires, the runtime suspend/resume callbacks are
> not triggered, leaving the card in an uninitialized state.
> 
> To address this, export sdio_reinit_card() so that client drivers can
> explicitly trigger reinitialization after powering the card back on,
> ensuring proper device state regardless of runtime PM behavior.
> 
> This change enables more robust handling of power-managed SDIO devices
> in scenarios where runtime PM is disabled or insufficient.

This seems to lack an actual users.

If we keep getting these malicious add unused export patches from
certain companies over and over we'll really have to start consider
banning them from kernel development.