From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail143.messagelabs.com (mail143.messagelabs.com [216.82.254.35]) by kanga.kvack.org (Postfix) with ESMTP id 7A3888D0039 for ; Sun, 6 Mar 2011 08:20:05 -0500 (EST) Date: Sun, 6 Mar 2011 13:19:55 +0000 From: Alan Cox Subject: Re: [PATCH] Make /proc/slabinfo 0400 Message-ID: <20110306131955.722d9bd5@lxorguk.ukuu.org.uk> In-Reply-To: <20110305162508.GA11120@thunk.org> References: <1299270709.3062.313.camel@calx> <1299271377.2071.1406.camel@dan> <1299272907.2071.1415.camel@dan> <1299275042.2071.1422.camel@dan> <1299279756.3062.361.camel@calx> <20110305162508.GA11120@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Ted Ts'o Cc: Matt Mackall , Pekka Enberg , Dan Rosenberg , Linus Torvalds , Dave Hansen , cl@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Ingo Molnar , Andrew Morton > If we had wrappers for the most common cases, then any cases that were > left that used copy_from_user() explicitly could be flagged and > checked by hand, since they would be exception, and not the rule. Arjan's copy_from_user validation code already does verification checks on the copies using gcc magic. Some of the others might be useful - kmalloc_from_user() is a fairly obvious interface, a copy_from_user_into() interface where you pass the destination object and its actual length as well is mostly covered by Arjan's stuff. Alan -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org