linux-kernel - Re: [GIT PULL] Native Linux KVM tool for 3.1

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: <20110725113258.GA26133@elte.hu>
Date:	Mon, 25 Jul 2011 13:32:58 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Alexander Graf <agraf@...e.de>, Pekka Enberg <penberg@...nel.org>,
	Jan Kiszka <jan.kiszka@....de>, torvalds@...ux-foundation.org,
	avi@...hat.com, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	gorcunov@...il.com, levinsasha928@...il.com, asias.hejun@...il.com,
	prasadjoshi124@...il.com
Subject: Re: [GIT PULL] Native Linux KVM tool for 3.1


* Christoph Hellwig <hch@...radead.org> wrote:

> On Mon, Jul 25, 2011 at 01:08:10PM +0200, Ingo Molnar wrote:
>
> > Fact is that developing ABIs within an integrated project is 
> > *amazingly* powerful. You should try it one day, instead of 
> > criticizing it :-)
> 
> I've been doing this long before you declare it the rosetta stone.  
> Some of the worst ABIs I know come from that kind of development, 
> e.g. all the ioctls we have in xfs, inherited from the "tightly 
> integrated" IRIX development cycle.

As i said it's not a guarantee, you can mess up even under the best 
of circumstances.

Also, arguably a filesystem is constrainted wrt. ABIs: it's just one 
filesystem which pretty much pushes it towards ioctls which in turn 
is often an unstructured breeding ground for mess.

Thanks,

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