Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262008AbUK3IJE (ORCPT ); Tue, 30 Nov 2004 03:09:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262014AbUK3IJE (ORCPT ); Tue, 30 Nov 2004 03:09:04 -0500 Received: from wproxy.gmail.com ([64.233.184.203]:1035 "EHLO wproxy.gmail.com") by vger.kernel.org with ESMTP id S262008AbUK3IJA (ORCPT ); Tue, 30 Nov 2004 03:09:00 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=D8ZfssHj13PDIjJKK/5nBIItpFfp2tCt7U3LKDB7c5jZ8D1+suGA6xGqEvWfNTuN5/cN9MUzXgdan/RsfT3QekVc3gJEDVUNIVOTe2B/4y7HEcp4LXkbBDqKbMuaXw2Rzxq4hVYFC8L2FByjphekjXJ3o8jQB3ajZy51RjwZ7KQ= Message-ID: <81b0412b04113000087fc8391e@mail.gmail.com> Date: Tue, 30 Nov 2004 09:08:59 +0100 From: Alex Riesen Reply-To: Alex Riesen To: David Woodhouse Subject: Re: [RFC] Splitting kernel headers and deprecating __KERNEL__ Cc: Linus Torvalds , Paul Mackerras , Greg KH , Matthew Wilcox , David Howells , hch@infradead.org, aoliva@redhat.com, linux-kernel@vger.kernel.org, libc-hacker@sources.redhat.com In-Reply-To: <1101721336.21273.6138.camel@baythorne.infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <19865.1101395592@redhat.com> <20041125165433.GA2849@parcelfarce.linux.theplanet.co.uk> <1101406661.8191.9390.camel@hades.cambridge.redhat.com> <20041127032403.GB10536@kroah.com> <16810.24893.747522.656073@cargo.ozlabs.ibm.com> <1101721336.21273.6138.camel@baythorne.infradead.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 912 Lines: 20 On Mon, 29 Nov 2004 09:42:16 +0000, David Woodhouse wrote: > I've lost track of the number of times things have broken because of > incorrect use of kernel headers from userspace. That's what we're trying > to fix -- by putting only the bits which are _supposed_ to be visible > into files which userspace sees, where we know they define part of the > userspace API and hence we can be extremely careful when editing them. how about generating the user-visible interfaces and structures from the headers using something like sparse and defined annotations? I.e.: struct iovec { void __user *iov_base; __kernel_size_t iov_len; } __user_api__; - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/