| 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
| ||
|
Message-ID: <20101019005819.24c8d373@lxorguk.ukuu.org.uk> Date: Tue, 19 Oct 2010 00:58:19 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: David Miller <davem@...emloft.net> Cc: paul.gortmaker@...driver.com, luca@...cax.com.ar, jon.maloy@...csson.com, tipc-discussion@...ts.sourceforge.net, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: Linux 2.6.35/TIPC 2.0 ABI breaking changes On Mon, 18 Oct 2010 15:17:08 -0700 (PDT) David Miller <davem@...emloft.net> wrote: > From: Paul Gortmaker <paul.gortmaker@...driver.com> > Date: Mon, 18 Oct 2010 16:42:33 -0400 > > > If you have access to the user space code in question, you can just > > switch behaviour semantics based on the results of a uname call, knowing > > that this change was included in versions since approx last Feb. There > > is also /proc/version which can be parsed manually if you prefer. > > Requiring userspace to check kernel versioning information in order > to user an exported userspace API correctly is _ALWAYS_ _WRONG_. > > You cannot and must not make backwards incompatible changes to > userspace interfaces. > > Really, you can't. In which case given that most distros are shipping older stuff and care about ABI stability presumably the bug should get fixed for 2.6.36 ? -- 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