From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "Cress, Andrew R" <andrew.r.cress@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Validating Pointers
Date: Thu, 26 Jul 2001 12:45:30 -0300 [thread overview]
Message-ID: <20010726124529.B2548@conectiva.com.br> (raw)
In-Reply-To: <9678C2B4D848D41187450090276D1FAE1008EAA8@FMSMSX32>
In-Reply-To: <9678C2B4D848D41187450090276D1FAE1008EAA8@FMSMSX32>; from andrew.r.cress@intel.com on Thu, Jul 26, 2001 at 08:36:49AM -0700
Em Thu, Jul 26, 2001 at 08:36:49AM -0700, Cress, Andrew R escreveu:
>
> 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?
normally one uses get_user & friends and copy_from_user and friends
checking its return and returning -EFAULT if they fail
next prev parent reply other threads:[~2001-07-26 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 15:36 Validating Pointers Cress, Andrew R
2001-07-26 15:45 ` Arnaldo Carvalho de Melo [this message]
[not found] <no.id>
2001-07-26 15:52 ` Alan Cox
2001-07-26 17:09 ` tpepper
2001-07-26 17:12 ` Alan Cox
2001-07-27 3:19 ` tpepper
2001-07-27 9:47 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010726124529.B2548@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=andrew.r.cress@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox