linux-kernel - Re: [PATCH 2/2] sound: make OSS device number claiming optional

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:	Wed, 5 Aug 2009 12:15:51 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	Colin Guthrie <cguthrie@...driva.org>, Tejun Heo <teheo@...e.de>,
	Greg KH <greg@...ah.com>, Al Viro <viro@....linux.org.uk>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] sound: make OSS device number claiming optional

> Not really :)  The soundcore is only for OSS device files.  As long as
> you use only ALSA-native APIs, you don't need it.  But, currently it's
> loaded and initialized just because of the module dependency.  This is
> no bug but also not an intended feature.

Sure for the ALSA device node it makes sense because ALSA is the mux for
it. Fortunately soundcore is tiny anyway.

> > This makes it worse.
> 
> Well, the only regression would be the case where you create static
> /dev/dsp (or else) devices and let auto-loading through sound-slot-*
> or sound-service-*-* aliases.  Of course, this still works if you
> load soundcore in some way.

Unless some ugly cuse hack got there first.

> What I suggested in the above is to cut off an unneeded dependency
> between soundcore and ALSA-native stuff instead of hacking soundcore.
> It won't change anything else, so everything else can coexist as
> before.

Agreed - but that is really a separate issue to having something break
the soundcore by being rude.

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