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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A794FB9.30403@mandriva.org>
Date:	Wed, 05 Aug 2009 10:24:09 +0100
From:	Colin Guthrie <cguthrie@...driva.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Tejun Heo <teheo@...e.de>, Greg KH <greg@...ah.com>,
	Al Viro <viro@....linux.org.uk>, Takashi Iwai <tiwai@...e.de>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] sound: make OSS device number claiming optional

'Twas brillig, and Alan Cox at 05/08/09 10:15 did gyre and gimble:
> On Wed, 05 Aug 2009 15:40:42 +0900
> Tejun Heo <teheo@...e.de> wrote:
> 
>> If any OSS support is enabled, regardless of built-in or module,
>> sound_core claims full OSS major number (that is, the old 0-255
>> region) to trap open attempts and request sound module automatically.
>> This feature is redundant as chrdev already has such mechanism and no
>> longer used by modern distros.  This preemptive claiming prevents
>> alternative OSS implementation.
>>
>> This patch makes the preclaiming optional and adds a config option
>> SOUND_OSS_CORE_PRECLAIM and kernel parameter soundcore.preclaim_oss to
>> control whether preclaim is enabled or not.  This allows distros and
>> developers to try new things without rebuilding kernel.
> 
> This looks like a random private devel hack sand I don't see why it's
> appropriate for mainstream, especially as these "new things" don't exist
> mainstream either.

While I'm not familiar enough with the kernel itself to comment on *how* 
the patch works, the principle is quite important here.

As far as I know most distros enable snd-*-oss module loading via a 
modprobe trick (e.g. in user space) so the change here shouldn't affect 
this approach.

However, I certainly want to experiment with osspd and while I hope it's 
going to be a good solution generally, it'll only make sense if the user 
chooses to use pulseaudio.

If the user decided they want to use pure alsa, then they'll have to 
drop back to using snd-*-oss for that instead.

This is all something I'd like to enable without making the user change 
kernels based on a preference.

So if this patch is not accepted, I'd still like to see the kernel not 
claim this device number, and leave it up to userspace to load the modules.

Sorry if this is not all factually accurate, but I think i've got the 
gist right! :)

-- 

Colin Guthrie
cguthrie(at)mandriva.org
http://colin.guthr.ie/

Day Job:
   Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
   Mandriva Linux Contributor [http://www.mandriva.com/]
   PulseAudio Hacker [http://www.pulseaudio.org/]
   Trac Hacker [http://trac.edgewall.org/]
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ