linux-kernel - Re: [Alsa-user] another in kernel alsa update that breaks backward compatibilty?

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]

Date:	Wed, 9 Aug 2006 19:44:03 +0300
From:	Sergei Steshenko <steshenko_sergei@...t.ru>
To:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
Cc:	"Sam Ravnborg" <sam@...nborg.org>,
	"Benoit Fouet" <benoit.fouet@...plelabs.com>,
	"Gene Heskett" <gene.heskett@...izon.net>,
	alsa-user@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [Alsa-user] another in kernel alsa update that breaks backward
 compatibilty?

On Wed, 9 Aug 2006 12:36:23 -0400
"Dmitry Torokhov" <dmitry.torokhov@...il.com> wrote:

> On 8/9/06, Sergei Steshenko <steshenko_sergei@...t.ru> wrote:
> > On Wed, 9 Aug 2006 18:00:43 +0200
> > Sam Ravnborg <sam@...nborg.org> wrote:
> >
> > > On Wed, Aug 09, 2006 at 05:56:57PM +0200, Benoit Fouet wrote:
> > > > >
> > > > >Demand stable ABI.
> > > > >
> > > > >
> > > > >
> > > > sorry for the noise, but it's been a while now since i began reading
> > > > mails from this list, and i must admit i don't always (never?) see the
> > > > point of such messages...
> > > > if you can help me understand, i'll be very happy to get something more
> > > > detailed from you...
> > > Documentation/stable_api_nonsense.txt
> > >
> > >       Sam
> > >
> >
> > I love senselessness and technical incompetence of the document.
> >
> > As I was taught at school, to prove that a statement is wrong one
> > has to prove that it is wrong once.
> >
> 
> Yep, the only trick is that you need a valid proof ;)
> 
> > Regardless of what the document says stable ABI can be achieved
> > today - run a chosen Linux kernel version + chosen ALSA version under XEN or
> > similar, and assign sound card to these (chosen Linux kernel version +
> > chosen ALSA version).
> >
> > Redirect sound ('ncat' + friends) to this (chosen Linux kernel version +
> > chosen ALSA version) from your kernel in which developers refuse
> > to ensure stable ABI.
> >
> > Because of the chosen (kernel+ALSA) you have stable ABI regardless
> > of what Documentation/stable_api_nonsense.txt says and ALSA + kernel
> > developers think.
> >
> 
> You are confused. By your logic you do not need XEN at all - just take
> a kernel version + alsa and never change/update it - and viola!
> "stable" ABI.
> 

I simply described how one ABI (ALSA <-> kernel in this case) can
be stabilized, while new non-ALSA related features (and potentially
unstable ABI) can still be had.

If computer has enough resources, practically every ABI can be
stabilized (if desired) this way - as long as the ABI is PCI slot
related.

That is, I can, for example, stabilize ALSA-kernel interface choosing
(ALSA 1.0.11 + kernel 2.6.17) and I can stabilize TV card interface
using (whatever v4l + kernel 2.6.18), etc,

--Sergei.
-- 
Visit my http://appsfromscratch.berlios.de/ open source project.
-
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/