linux-kernel - Re: [PATCH 1/1] mmc: add MODALIAS linkage for MMC/SD 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun, 25 Jan 2009 17:00:11 +0100
From:	Kay Sievers <kay.sievers@...y.org>
To:	Pierre Ossman <drzeus-mmc@...eus.cx>
Cc:	Andy Whitcroft <apw@...onical.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] mmc: add MODALIAS linkage for MMC/SD devices

On Sun, Jan 25, 2009 at 16:48, Pierre Ossman <drzeus-mmc@...eus.cx> wrote:
> On Sun, 25 Jan 2009 00:45:46 +0100
> Kay Sievers <kay.sievers@...y.org> wrote:
>
>> On Sat, Jan 24, 2009 at 18:56, Pierre Ossman <drzeus-mmc@...eus.cx> wrote:
>> >
>> > Well, as long as we're on the track of temporary hack, we might as well
>> > just export "mmc_block" as the modalias. Or would there be any
>> > side-effects to that?
>>
>> The common format is to prefix with "<subsystem>:". Something like
>> "mmc:block" sounds fine to me.
>>
>
> My point was to have the kernel explicitly ask for the module it wants
> as there is no decent device to driver mapping scheme.

Yep, which is what we do not want. Aliases are "aliases", and not
"module names". We need to add a matching alias to the module then.
Direct module names can not properly defined/blacklisted in userspace,
and we would need to work around that.
Every modalias should be
"<subsystem>:<whatever-name-fits-for-the-subsystem>" to plug properly
into the autoloading infrastructure. We rather have no modalias at
all, then a kernel module name there.

Thanks,
Kay
--
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/