linux-kernel - Re: 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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5h8tm3h9pi.wl-tiwai@suse.de>
Date:   Thu, 11 May 2017 14:14:17 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     Takashi Sakamoto <o-takashi@...amocchi.jp>
Cc:     Christoph Hellwig <hch@....de>, linux-kernel@...r.kernel.org,
        Linus Torvalds <torvalds@...uxfoundation.org>,
        alsa-devel@...a-project.org
Subject: Re: future of sounds/oss

On Thu, 11 May 2017 12:36:47 +0200,
Takashi Sakamoto wrote:
> 
> Oops. I misunderstand to have discussion about stuffs in
> 'sound/core/oss/*', because the compatibility layer also includes
> abuses of set_fs() and I'm interested in it today...

Yes, the stuff in sound/core/oss required an intensive surgery to get
rid of set_fs().  But this resulted in a good cleanup of the
duplicated copy/silence callbacks in the end.

> For stuffs in 'sound/oss', we should certainly have care of points
> which Iwai-san mentioned. If we get rid of it, we can also apply diet
> to 'soundcore' module which gives 'sound' class but include some
> helper functions just for Open Sound System drivers.

Right, that's low-hanging fruits we can take once after confirming the
removal of OSS drivers.  The soundcore module can be removed and
integrated into the ALSA OSS emulation stuff, for example.


thanks,

Takashi