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: <1154639566.23655.132.camel@localhost.localdomain>
Date:	Thu, 03 Aug 2006 22:12:46 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Willy Tarreau <w@....eu>
Cc:	Zachary Amsden <zach@...are.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>, greg@...ah.com,
	Andrew Morton <akpm@...l.org>,
	Christoph Hellwig <hch@...radead.org>,
	Rusty Russell <rusty@...tcorp.com.au>, Jack Lo <jlo@...are.com>
Subject: Re: A proposal - binary

Ar Iau, 2006-08-03 am 22:29 +0200, ysgrifennodd Willy Tarreau:
> I think that the issue Zach tried to cover is the current inability to
> keep the same binary module across multiple kernel versions. That's why
> he compared modules<->kernel to ELF<->glibc. In that sense, he's right.

I think thats why he's wrong.

The interface for a hypedvisor is

      Kernel -> Something -> Hypedvisor

The kernel->something interface can change randomly by day of week, who
cares. A better analogy would be a device driver - we recompile device
drivers each kernel variant, which change their internal interfaces, we 
redesign their locking but we don't have to change the hardware.

Ditto talking to the hypedvisor. The ABI is the hypedvisor syscall/trap
interface not the kernel module interface. As such insmod is just fine.

Alan

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