Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261576AbUFJPLG (ORCPT ); Thu, 10 Jun 2004 11:11:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261582AbUFJPLG (ORCPT ); Thu, 10 Jun 2004 11:11:06 -0400 Received: from kinesis.swishmail.com ([209.10.110.86]:23053 "EHLO kinesis.swishmail.com") by vger.kernel.org with ESMTP id S261576AbUFJPLE (ORCPT ); Thu, 10 Jun 2004 11:11:04 -0400 Message-ID: <40C87DAF.902@techsource.com> Date: Thu, 10 Jun 2004 11:26:39 -0400 From: Timothy Miller MIME-Version: 1.0 To: Linus Torvalds CC: "Robert T. Johnson" , Al Viro , Linux Kernel Subject: Re: Finding user/kernel pointer bugs [no html] References: <1086838266.32059.320.camel@dooby.cs.berkeley.edu> <40C87934.2060505@techsource.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 736 Lines: 25 Linus Torvalds wrote: >>If you really want to force user space accesses to follow certain rules, >>make them longs or structs (or at least void *) (depending on >>architecture) so that only the proper user-space-access functions can >>interpret them. > > > .. and this would be a total disaster. > > Think about it. The user pointer isn't just a "value". It has a type it > points to. We want to do Makes sense. Too many things my short-sighted suggestion didn't account for. - 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/