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

Date:	Wed, 9 Aug 2006 13:54:29 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Sergei Steshenko" <steshenko_sergei@...t.ru>
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 8/9/06, Sergei Steshenko <steshenko_sergei@...t.ru> wrote:
> On Wed, 9 Aug 2006 12:36:23 -0400
> "Dmitry Torokhov" <dmitry.torokhov@...il.com> wrote:
> >
> > 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.
>

And in extreme case once you "stablizie" everything you end up with a
system that is not upgradeable at all.

> 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,
>

But you are not stabilizing ABI, you are freezing a subsystem. Stable
ABI does not mean that bugs do not get fixed and new hardware support
is not being addeed, as in your case.

-- 
Dmitry
-
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/