d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Document the various reasons for EINVAL.

Browse Source 
Document the flaw that `offset' is required to be page-aligned, in the
BUGS section.
This commit is contained in:
joerg 1997-01-08 12:02:15 +00:00
parent 905959b15e
commit 7ef3ec1dbd
1 changed files with 21 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
lib/libc/sys/mmap.2
View File

@ -180,20 +180,28 @@ was not open for writing.
.It Bq Er EBADF
.Fa Fd
is not a valid open file descriptor.
.\".It Bq Er EINVAL
.\"One of
.\".Dv MAP_ANON
.\"or
.\".Dv MAP_FILE
.\"was not specified as part of the
.\".Fa flags
.\"parameter.
.It Bq Er EINVAL
.Dv MAP_FIXED
was specified and the
.I addr
parameter was not page aligned.
.Fa Fd
.Fa addr
parameter was not page aligned, or part of the desired address space
resides out of the valid address space for a user process.
.It Bq Er EINVAL
.Fa Len
was negative.
.It Bq Er EINVAL
.Dv MAP_ANON
was specified and the
.Fa fd
parameter was not -1.
.It Bq Er EINVAL
.Dv MAP_ANON
has not been specified and
.Fa fd
did not reference a regular or character special file.
.It Bq Er EINVAL
.Fa Offset
was not page-aligned. (See BUGS below.)
.It Bq Er ENOMEM
.Dv MAP_FIXED
was specified and the
@ -226,3 +234,5 @@ the filesystem code that causes the limit to be further restricted to
Another reason for the 2GB limit is that filesystem metadata can
reside at negative offsets.
We currently can only deal with page aligned file offsets.