Return values and error codes - BrainDump

In this third part of a seven-part series on Linux I/O file system calls, you'll learn how to use the mmap() system call, which will give you some flexibility when handling files. This article is excerpted from chapter four of the book Linux System Programming: Talking Directly to the Kernel and C Library, written by Robert Love (O'Reilly, 2007; ISBN: 0596009585). Copyright © 2007 O'Reilly Media, Inc. All rights reserved. Used with permission from the publisher. Available from booksellers or direct from O'Reilly Media.

TABLE OF CONTENTS:

By: O'Reilly Media

Poor Best

Rating:

/ 5

December 11, 2008

print this article

SEARCH DEV SHED

TOOLS YOU CAN USE

On success, a call to mmap() returns the location of the mapping. On failure, the call returns MAP_FAILED, and setserrnoappropriately. A call tommap()never returns0.

Possibleerrnovalues include:

EACCESS
   The given file descriptor is not a regular file, or the
   mode with which it was opened conflicts withprot
   orflags.

EAGAIN
The file has been locked via a file lock.

EBADF
The given file descriptor is not valid.

EINVAL
One or more of the parametersaddr,len, oroff
are invalid.

ENFILE
The system-wide limit on open files has been
reached.

ENODEV
The filesystem on which the file to map resides does
not support memory mapping.

ENOMEM
The process does not have enough memory.

EOVERFLOW
The result ofaddr+lenexceeds the size of the
address space.

EPERM
PROT_EXECwas given, but the filesystem is mounted
noexec.

Next: Associated signals >>