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: <20090805141157.6d6b857c@lxorguk.ukuu.org.uk>
Date:	Wed, 5 Aug 2009 14:11:57 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Tejun Heo <teheo@...e.de>
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

> If we're gonna do that, we might as well just rip off the pointless
> 'claim everything so we can use our own module alises' code from
> sound_core.c and be done with it.  That really is the only problem.

The interface expected is the sound_register_* interface and the sharing
is likewise expected so you could for example mix OSS. CUSE and ALSA oss
emulation drivers on the same system at the same time.

Rewriting sound_register* in terms of minor number allocations using the
fact modern kernels have better allocators for devices would also be
preferable to the weird module hacks initially proposed. I guess a
starting point would be to tweak soundcore to generate both message sets
itself for a year and then pull the old stuff out.

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/