.\" This documentation was generated from the book titled "The Linux Kernel API", which is part of the Linux kernel source. .\" .\" This documentation comes with the following legal notice: .\" .\" This documentation is free software; you can redistribute .\" it and/or modify it under the terms of the GNU General Public .\" License as published by the Free Software Foundation; either .\" version 2 of the License, or (at your option) any later .\" version. .\" .\" This program is distributed in the hope that it will be .\" useful, but WITHOUT ANY WARRANTY; without even the implied .\" warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. .\" See the GNU General Public License for more details. .\" .\" You should have received a copy of the GNU General Public .\" License along with this program; if not, write to the Free .\" Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, .\" MA 02111-1307 USA .\" .\" For more details see the file COPYING in the source .\" distribution of Linux. .\" .\" For comments on the formatting of this manpage, please contact Michael Still .\" This manpage has been automatically generated by docbook2man .\" from a DocBook document. This tool can be found at: .\" .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng . .TH "ACCESS_OK" "9" "06 August 2003" "" "" .SH NAME access_ok \- Checks if a user space pointer is valid .SH SYNOPSIS .sp \fB .sp access_ok ( \fItype\fB, \fIaddr\fB, \fIsize\fB); \fR .SH "ARGUMENTS" .TP \fB\fItype\fB\fR Type of access: VERIFY_READ or VERIFY_WRITE. Note that VERIFY_WRITE is a superset of VERIFY_READ - if it is safe to write to a block, it is always safe to read from it. .TP \fB\fIaddr\fB\fR User space pointer to start of block to check .TP \fB\fIsize\fB\fR Size of block to check .SH "CONTEXT" .PP User context only. This function may sleep. .SH "DESCRIPTION" .PP Checks if a pointer to a block of memory in user space is valid. .PP Returns true (nonzero) if the memory block may be valid, false (zero) if it is definitely invalid. .PP Note that, depending on architecture, this function probably just checks that the pointer is in the user space range - after calling this function, memory access functions may still return -EFAULT. .SH "ABOUT THIS DOCUMENT" .PP This documentation was generated with kernel version 2.6.0.