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]

Message-ID: <4A796E5D.2090707@suse.de>
Date:	Wed, 05 Aug 2009 20:34:53 +0900
From:	Tejun Heo <teheo@...e.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Takashi Iwai <tiwai@...e.de>,
	Colin Guthrie <cguthrie@...driva.org>,
	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

Alan Cox wrote:
>>> 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.

Sigh, does the wording really have to be 'ugly' and 'rude'?
sound_core.c itself is a strange hack at this point.  :-(

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