Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 26 Jul 2001 11:51:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 26 Jul 2001 11:51:46 -0400 Received: from router-100M.swansea.linux.org.uk ([194.168.151.17]:26638 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Thu, 26 Jul 2001 11:51:32 -0400 Subject: Re: Validating Pointers To: andrew.r.cress@intel.com (Cress, Andrew R) Date: Thu, 26 Jul 2001 16:52:48 +0100 (BST) Cc: linux-kernel@vger.kernel.org In-Reply-To: from "Cress, Andrew R" at Jul 26, 2001 08:36:49 AM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Original-Recipient: rfc822;linux-kernel-outgoing > Is there a general (correct) kernel subroutine to validate a pointer > received in a routine as input from the outside world? Is access_ok() a > good one to use? access_ok may do minimal checks, or no checking at all. The only point at which you can validate a user point is when you use copy*user and get/put_user to access the data. - 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/