linux-kernel - Re: A proposal

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: <44D3941D.7010303@goop.org>
Date:	Fri, 04 Aug 2006 11:38:21 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	David Lang <dlang@...italinsight.com>
CC:	Rusty Russell <rusty@...tcorp.com.au>,
	Andrew Morton <akpm@...l.org>, jeremy@...source.com,
	greg@...ah.com, zach@...are.com, linux-kernel@...r.kernel.org,
	torvalds@...l.org, hch@...radead.org, jlo@...are.com,
	xen-devel@...ts.xensource.com, simon@...source.com,
	ian.pratt@...source.com
Subject: Re: A proposal - binary

David Lang wrote:
> if it's only a source-level API this implies that when you move your 
> host kernel from 2.6.19 to 2.6.25 you would need to recompile your 
> 2.6.19 guest kernel to support the modifications. where are the 
> patches going to come from to do this?

No, the low-level interface between the kernel is an ABI, which will be 
as stable as your hypervisor author/vendor wants it to be (which is 
generally "very stable").  The question is whether that low-level 
interface is exposed to the rest of the kernel directly, or hidden 
behind a kernel-internal source-level API.

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