| 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: <20100824145643.GR12892@parisc-linux.org> Date: Tue, 24 Aug 2010 08:56:43 -0600 From: Matthew Wilcox <matthew@....cx> To: Chris Weiss <cweiss@...il.com> Cc: Vladislav Bolkhovitin <vst@...b.net>, James Bottomley <James.Bottomley@...e.de>, Mike Christie <michaelc@...wisc.edu>, linux-scsi@...r.kernel.org, Chetan Loke <chetanloke@...il.com>, linux-kernel@...r.kernel.org, scst-devel <scst-devel@...ts.sourceforge.net> Subject: Re: [Scst-devel] Fwd: Re: linuxcon 2010... On Tue, Aug 24, 2010 at 09:51:04AM -0500, Chris Weiss wrote: > ok now I'm confused, or maybe I'm not understanding ABI correctly, or > maybe you guys are using it in a way that is inconsistent with popular > convention. As a VMware user, I have experienced fully that the > kernel ABI changes in various places with every release. VMwares > drivers have to be constantly updated to match changes in kernel > function parameters and even what functions are available. You're talking about in-kernel ABI, which is constantly in flux. James is talking about user <-> kernel ABI, which is not supposed to change in an incompatible way. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- 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