linux-kernel - future of sounds/oss

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-next>] [day] [month] [year] [list]

Message-ID: <20170511082133.GA20304@lst.de>
Date:   Thu, 11 May 2017 10:21:33 +0200
From:   Christoph Hellwig <hch@....de>
To:     Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: future of sounds/oss

Ho Jaroslav, hi Takashi,

do you know who still uses the sound/oss drivers and why?  I've
recently been looking into getting rid of set_fs for using
copy_{from,to}_user and friends on kernel pointers, and the sound
code is a big abuser, both ALSA and the legacy OSS code.

But looking at the OSS code it's pretty grotty, and also appears
to be pretty much unmaintained except for global cleanups.  Is there
any chance we could look into getting rid of it over the next few
merge windows or are there people that rely on it?