linux-kernel - Re: [RFC 2/2] mmc: use SD/MMC host ID for block device name ID

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]

Date:	Tue, 01 Apr 2014 14:47:36 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	stefan@...er.ch, chris@...ntf.net, linux-mmc@...r.kernel.org
CC:	linux-tegra@...r.kernel.org, linux@....linux.org.uk,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC 2/2] mmc: use SD/MMC host ID for block device name ID

On 04/01/2014 02:35 PM, stefan@...er.ch wrote:
> From: Stefan Agner <stefan@...er.ch>
> 
> By using the SD/MMC host device ID as a starting point for block
> device numbering, one can reliably predict the first block device
> name (at least for the first controller).

That's not true. There's no guarantee that a device name/ID gets
released as soon as the SD card is removed; something might still have
it mounted for example.

The correct solution here is to use filesystem or partition UUIDs to
identify the device/partition, not to attempt to assign static device IDs.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/