linux-kernel - Re: [PATCH] mmc: add module parameter to set whether cards are assumed removable

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: <20091130124844.6ec0b8da@lxorguk.ukuu.org.uk>
Date:	Mon, 30 Nov 2009 12:48:44 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Adrian Hunter <adrian.hunter@...ia.com>
Cc:	Ben Hutchings <ben@...adent.org.uk>,
	"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"504391@...s.debian.org" <504391@...s.debian.org>,
	Wouter van Heyst <larstiq@...stiq.dyndns.org>
Subject: Re: [PATCH] mmc: add module parameter to set whether cards are
 assumed removable

> You do not cater for having more than one slot e.g. N900 has two:
> one internal non-removable and one external that is removable.
> 
> What about a sysfs entry instead e.g.
> 
>  /sys/class/mmc-host/mmc*/nonremovable

That continues the assumption that the user will somehow ever know about
this stuff and configure it. Almost nobody will.

Not only does it need to be per-port there needs to be a credible
description of how it will automatically happen - who configures it,
when, how and is the data needed available.

--
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/