xref: /freebsd-13.1/lib/libc/sys/open.2 (revision 821467b5)
1.\" Copyright (c) 1980, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. Neither the name of the University nor the names of its contributors
13.\"    may be used to endorse or promote products derived from this software
14.\"    without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
28.\"     @(#)open.2	8.2 (Berkeley) 11/16/93
29.\" $FreeBSD$
30.\"
31.Dd April 22, 2022
32.Dt OPEN 2
33.Os
34.Sh NAME
35.Nm open , openat
36.Nd open or create a file for reading, writing or executing
37.Sh LIBRARY
38.Lb libc
39.Sh SYNOPSIS
40.In fcntl.h
41.Ft int
42.Fn open "const char *path" "int flags" "..."
43.Ft int
44.Fn openat "int fd" "const char *path" "int flags" "..."
45.Sh DESCRIPTION
46The file name specified by
47.Fa path
48is opened
49for either execution or reading and/or writing as specified by the
50argument
51.Fa flags
52and the file descriptor returned to the calling process.
53The
54.Fa flags
55argument may indicate the file is to be
56created if it does not exist (by specifying the
57.Dv O_CREAT
58flag).
59In this case
60.Fn open
61and
62.Fn openat
63require an additional argument
64.Fa "mode_t mode" ,
65and the file is created with mode
66.Fa mode
67as described in
68.Xr chmod 2
69and modified by the process' umask value (see
70.Xr umask 2 ) .
71.Pp
72The
73.Fn openat
74function is equivalent to the
75.Fn open
76function except in the case where the
77.Fa path
78specifies a relative path.
79For
80.Fn openat
81and relative
82.Fa path ,
83the file to be opened is determined relative to the directory
84associated with the file descriptor
85.Fa fd
86instead of the current working directory.
87The
88.Fa flag
89parameter and the optional fourth parameter correspond exactly to
90the parameters of
91.Fn open .
92If
93.Fn openat
94is passed the special value
95.Dv AT_FDCWD
96in the
97.Fa fd
98parameter, the current working directory is used
99and the behavior is identical to a call to
100.Fn open .
101.Pp
102When
103.Fn openat
104is called with an absolute
105.Fa path ,
106it ignores the
107.Fa fd
108argument.
109.Pp
110In
111.Xr capsicum 4
112capability mode,
113.Fn open
114is not permitted.
115The
116.Fa path
117argument to
118.Fn openat
119must be strictly relative to a file descriptor
120.Fa fd .
121.Fa path
122must not be an absolute path and must not contain ".." components
123which cause the path resolution to escape the directory hierarchy
124starting at
125.Fa fd .
126Additionally, no symbolic link in
127.Fa path
128may target absolute path or contain escaping ".." components.
129.Fa fd
130must not be
131.Dv AT_FDCWD .
132.Pp
133If the
134.Dv vfs.lookup_cap_dotdot
135.Xr sysctl 3
136MIB is set to zero, ".." components in the paths,
137used in capability mode,
138are completely disabled.
139If the
140.Dv vfs.lookup_cap_dotdot_nonlocal
141MIB is set to zero, ".." is not allowed if found on non-local filesystem.
142.Pp
143The flags specified are formed by
144.Em or Ns 'ing
145the following values
146.Pp
147.Bd -literal -offset indent -compact
148O_RDONLY	open for reading only
149O_WRONLY	open for writing only
150O_RDWR		open for reading and writing
151O_EXEC		open for execute only
152O_SEARCH	open for search only, an alias for O_EXEC
153O_NONBLOCK	do not block on open
154O_APPEND	append on each write
155O_CREAT		create file if it does not exist
156O_TRUNC		truncate size to 0
157O_EXCL		error if create and file exists
158O_SHLOCK	atomically obtain a shared lock
159O_EXLOCK	atomically obtain an exclusive lock
160O_DIRECT	eliminate or reduce cache effects
161O_FSYNC		synchronous writes (historical synonym for O_SYNC)
162O_SYNC		synchronous writes
163O_DSYNC		synchronous data writes
164O_NOFOLLOW	do not follow symlinks
165O_NOCTTY	ignored
166O_TTY_INIT	ignored
167O_DIRECTORY	error if file is not a directory
168O_CLOEXEC	set FD_CLOEXEC upon open
169O_VERIFY	verify the contents of the file
170O_RESOLVE_BENEATH	path resolution must not cross the fd directory
171O_PATH		record only the target path in the opened descriptor
172O_EMPTY_PATH	openat, open file referenced by fd if path is empty
173.Ed
174.Pp
175Opening a file with
176.Dv O_APPEND
177set causes each write on the file
178to be appended to the end.
179If
180.Dv O_TRUNC
181is specified and the
182file exists, the file is truncated to zero length.
183If
184.Dv O_EXCL
185is set with
186.Dv O_CREAT
187and the file already
188exists,
189.Fn open
190returns an error.
191This may be used to
192implement a simple exclusive access locking mechanism.
193If
194.Dv O_EXCL
195is set and the last component of the pathname is
196a symbolic link,
197.Fn open
198will fail even if the symbolic
199link points to a non-existent name.
200If the
201.Dv O_NONBLOCK
202flag is specified and the
203.Fn open
204system call would result
205in the process being blocked for some reason (e.g., waiting for
206carrier on a dialup line),
207.Fn open
208returns immediately.
209The descriptor remains in non-blocking mode for subsequent operations.
210.Pp
211If
212.Dv O_SYNC
213is used in the mask, all writes will
214immediately and synchronously be written to disk.
215.Dv O_FSYNC
216is an historical synonym for
217.Dv O_SYNC .
218.Pp
219If
220.Dv O_DSYNC
221is used in the mask, all data and metadata required to read the data will be
222synchronously written to disk, but changes to metadata such as file access and
223modification timestamps may be written later.
224.Pp
225If
226.Dv O_NOFOLLOW
227is used in the mask and the target file passed to
228.Fn open
229is a symbolic link then the
230.Fn open
231will fail.
232.Pp
233When opening a file, a lock with
234.Xr flock 2
235semantics can be obtained by setting
236.Dv O_SHLOCK
237for a shared lock, or
238.Dv O_EXLOCK
239for an exclusive lock.
240If creating a file with
241.Dv O_CREAT ,
242the request for the lock will never fail
243(provided that the underlying file system supports locking).
244.Pp
245.Dv O_DIRECT
246may be used to minimize or eliminate the cache effects of reading and writing.
247The system will attempt to avoid caching the data you read or write.
248If it cannot avoid caching the data,
249it will minimize the impact the data has on the cache.
250Use of this flag can drastically reduce performance if not used with care.
251.Pp
252.Dv O_NOCTTY
253may be used to ensure the OS does not assign this file as the
254controlling terminal when it opens a tty device.
255This is the default on
256.Fx ,
257but is present for
258.Tn POSIX
259compatibility.
260The
261.Fn open
262system call will not assign controlling terminals on
263.Fx .
264.Pp
265.Dv O_TTY_INIT
266may be used to ensure the OS restores the terminal attributes when
267initially opening a TTY.
268This is the default on
269.Fx ,
270but is present for
271.Tn POSIX
272compatibility.
273The initial call to
274.Fn open
275on a TTY will always restore default terminal attributes on
276.Fx .
277.Pp
278.Dv O_DIRECTORY
279may be used to ensure the resulting file descriptor refers to a
280directory.
281This flag can be used to prevent applications with elevated privileges
282from opening files which are even unsafe to open with
283.Dv O_RDONLY ,
284such as device nodes.
285.Pp
286.Dv O_CLOEXEC
287may be used to set
288.Dv FD_CLOEXEC
289flag for the newly returned file descriptor.
290.Pp
291.Dv O_VERIFY
292may be used to indicate to the kernel that the contents of the file should
293be verified before allowing the open to proceed.
294The details of what
295.Dq verified
296means is implementation specific.
297The run-time linker (rtld) uses this flag to ensure shared objects have
298been verified before operating on them.
299.Pp
300.Dv O_RESOLVE_BENEATH
301returns
302.Er ENOTCAPABLE
303if any intermediate component of the specified relative path does not
304reside in the directory hierarchy beneath the starting directory.
305Absolute paths or even the temporal escape from beneath of the starting
306directory is not allowed.
307.Pp
308When
309.Fa fd
310is opened with
311.Dv O_SEARCH ,
312execute permissions are checked at open time.
313The
314.Fa fd
315may not be used for any read operations like
316.Xr getdirentries 2 .
317The primary use for this descriptor will be as the lookup descriptor for the
318.Fn *at
319family of functions.
320.Pp
321.Dv O_PATH
322returns a file descriptor that can be used as a directory file descriptor for
323.Xr openat 2
324and other system calls taking a file descriptor argument, like
325.Xr fstatat 2
326and others.
327The other functionality of the returned file descriptor is limited to
328the descriptor-level operations.
329It can be used for
330.Bl -tag -width readlinkat(2) -offset indent -compact
331.It Xr fcntl 2
332but advisory locking is not allowed
333.It Xr dup 2
334.It Xr close 2
335.It Xr fstat 2
336.It Xr fexecve 2
337.It Dv SCM_RIGHTS
338can be passed over a
339.Xr unix 4
340socket using a
341.Dv SCM_RIGHTS
342message
343.It Xr kqueue 2
344using for
345.Dv EVFILT_VNODE
346.It Xr readlinkat 2
347.El
348But operations like
349.Xr read 2 ,
350.Xr ftruncate 2 ,
351and any other that operate on file and not on file descriptor (except
352.Xr fstat 2 ),
353are not allowed.
354.Pp
355A file descriptor created with the
356.Dv O_PATH
357flag can be opened into normal (operable) file descriptor by
358specifying it as the
359.Fa fd
360argument to
361.Fn openat
362with empty
363.Fa path
364and flag
365.Dv O_EMPTY_PATH .
366Such an open behaves as if the current path of the file referenced by
367.Fa fd
368is passed, except that the path walk permissions are not checked.
369See also the description of
370.Dv AT_EMPTY_PATH
371flag for
372.Xr fstatat 2
373and related syscalls.
374.Pp
375If successful,
376.Fn open
377returns a non-negative integer, termed a file descriptor.
378It returns \-1 on failure.
379The file pointer used to mark the current position within the
380file is set to the beginning of the file.
381.Pp
382If a sleeping open of a device node from
383.Xr devfs 5
384is interrupted by a signal, the call always fails with
385.Er EINTR ,
386even if the
387.Dv SA_RESTART
388flag is set for the signal.
389A sleeping open of a fifo (see
390.Xr mkfifo 2 )
391is restarted as normal.
392.Pp
393When a new file is created it is given the group of the directory
394which contains it.
395.Pp
396Unless
397.Dv O_CLOEXEC
398flag was specified,
399the new descriptor is set to remain open across
400.Xr execve 2
401system calls; see
402.Xr close 2 ,
403.Xr fcntl 2
404and
405.Dv O_CLOEXEC
406description.
407.Pp
408The system imposes a limit on the number of file descriptors
409open simultaneously by one process.
410The
411.Xr getdtablesize 2
412system call returns the current system limit.
413.Sh RETURN VALUES
414If successful,
415.Fn open
416and
417.Fn openat
418return a non-negative integer, termed a file descriptor.
419They return \-1 on failure, and set
420.Va errno
421to indicate the error.
422.Sh ERRORS
423The named file is opened unless:
424.Bl -tag -width Er
425.It Bq Er ENOTDIR
426A component of the path prefix is not a directory.
427.It Bq Er ENAMETOOLONG
428A component of a pathname exceeded 255 characters,
429or an entire path name exceeded 1023 characters.
430.It Bq Er ENOENT
431.Dv O_CREAT
432is not set and the named file does not exist.
433.It Bq Er ENOENT
434A component of the path name that must exist does not exist.
435.It Bq Er EACCES
436Search permission is denied for a component of the path prefix.
437.It Bq Er EACCES
438The required permissions (for reading and/or writing)
439are denied for the given flags.
440.It Bq Er EACCES
441.Dv O_TRUNC
442is specified and write permission is denied.
443.It Bq Er EACCES
444.Dv O_CREAT
445is specified,
446the file does not exist,
447and the directory in which it is to be created
448does not permit writing.
449.It Bq Er EPERM
450.Dv O_CREAT
451is specified, the file does not exist, and the directory in which it is to be
452created has its immutable flag set, see the
453.Xr chflags 2
454manual page for more information.
455.It Bq Er EPERM
456The named file has its immutable flag set and the file is to be modified.
457.It Bq Er EPERM
458The named file has its append-only flag set, the file is to be modified, and
459.Dv O_TRUNC
460is specified or
461.Dv O_APPEND
462is not specified.
463.It Bq Er ELOOP
464Too many symbolic links were encountered in translating the pathname.
465.It Bq Er EISDIR
466The named file is a directory, and the arguments specify
467it is to be modified.
468.It Bq Er EISDIR
469The named file is a directory, and the flags specified
470.Dv O_CREAT
471without
472.Dv O_DIRECTORY .
473.It Bq Er EROFS
474The named file resides on a read-only file system,
475and the file is to be modified.
476.It Bq Er EROFS
477.Dv O_CREAT
478is specified and the named file would reside on a read-only file system.
479.It Bq Er EMFILE
480The process has already reached its limit for open file descriptors.
481.It Bq Er ENFILE
482The system file table is full.
483.It Bq Er EMLINK
484.Dv O_NOFOLLOW
485was specified and the target is a symbolic link.
486.It Bq Er ENXIO
487The named file is a character special or block
488special file, and the device associated with this special file
489does not exist.
490.It Bq Er ENXIO
491.Dv O_NONBLOCK
492is set, the named file is a fifo,
493.Dv O_WRONLY
494is set, and no process has the file open for reading.
495.It Bq Er EINTR
496The
497.Fn open
498operation was interrupted by a signal.
499.It Bq Er EOPNOTSUPP
500.Dv O_SHLOCK
501or
502.Dv O_EXLOCK
503is specified but the underlying file system does not support locking.
504.It Bq Er EOPNOTSUPP
505The named file is a special file mounted through a file system that
506does not support access to it (e.g.\& NFS).
507.It Bq Er EWOULDBLOCK
508.Dv O_NONBLOCK
509and one of
510.Dv O_SHLOCK
511or
512.Dv O_EXLOCK
513is specified and the file is locked.
514.It Bq Er ENOSPC
515.Dv O_CREAT
516is specified,
517the file does not exist,
518and the directory in which the entry for the new file is being placed
519cannot be extended because there is no space left on the file
520system containing the directory.
521.It Bq Er ENOSPC
522.Dv O_CREAT
523is specified,
524the file does not exist,
525and there are no free inodes on the file system on which the
526file is being created.
527.It Bq Er EDQUOT
528.Dv O_CREAT
529is specified,
530the file does not exist,
531and the directory in which the entry for the new file
532is being placed cannot be extended because the
533user's quota of disk blocks on the file system
534containing the directory has been exhausted.
535.It Bq Er EDQUOT
536.Dv O_CREAT
537is specified,
538the file does not exist,
539and the user's quota of inodes on the file system on
540which the file is being created has been exhausted.
541.It Bq Er EIO
542An I/O error occurred while making the directory entry or
543allocating the inode for
544.Dv O_CREAT .
545.It Bq Er EINTEGRITY
546Corrupted data was detected while reading from the file system.
547.It Bq Er ETXTBSY
548The file is a pure procedure (shared text) file that is being
549executed and the
550.Fn open
551system call requests write access.
552.It Bq Er EFAULT
553The
554.Fa path
555argument
556points outside the process's allocated address space.
557.It Bq Er EEXIST
558.Dv O_CREAT
559and
560.Dv O_EXCL
561were specified and the file exists.
562.It Bq Er EOPNOTSUPP
563An attempt was made to open a socket (not currently implemented).
564.It Bq Er EINVAL
565An attempt was made to open a descriptor with an illegal combination
566of
567.Dv O_RDONLY ,
568.Dv O_WRONLY ,
569or
570.Dv O_RDWR ,
571and
572.Dv O_EXEC
573or
574.Dv O_SEARCH .
575.It Bq Er EINVAL
576The
577.Dv O_RESOLVE_BENEATH
578flag is specified and
579.Dv path
580is absolute.
581.It Bq Er EBADF
582The
583.Fa path
584argument does not specify an absolute path and the
585.Fa fd
586argument is
587neither
588.Dv AT_FDCWD
589nor a valid file descriptor open for searching.
590.It Bq Er ENOTDIR
591The
592.Fa path
593argument is not an absolute path and
594.Fa fd
595is neither
596.Dv AT_FDCWD
597nor a file descriptor associated with a directory.
598.It Bq Er ENOTDIR
599.Dv O_DIRECTORY
600is specified and the file is not a directory.
601.It Bq Er ECAPMODE
602.Dv AT_FDCWD
603is specified and the process is in capability mode.
604.It Bq Er ECAPMODE
605.Fn open
606was called and the process is in capability mode.
607.It Bq Er ENOTCAPABLE
608.Fa path
609is an absolute path,
610or contained a ".." component leading to a
611directory outside of the directory hierarchy specified by
612.Fa fd ,
613and the process is in capability mode.
614.It Bq Er ENOTCAPABLE
615The
616.Dv O_RESOLVE_BENEATH
617flag was provided, and the relative
618.Fa path
619escapes the
620.Ar fd
621directory.
622.El
623.Sh SEE ALSO
624.Xr chmod 2 ,
625.Xr close 2 ,
626.Xr dup 2 ,
627.Xr fexecve 2 ,
628.Xr fhopen 2 ,
629.Xr getdtablesize 2 ,
630.Xr getfh 2 ,
631.Xr lgetfh 2 ,
632.Xr lseek 2 ,
633.Xr read 2 ,
634.Xr umask 2 ,
635.Xr write 2 ,
636.Xr fopen 3 ,
637.Xr capsicum 4
638.Sh STANDARDS
639These functions are specified by
640.St -p1003.1-2008 .
641.Fx
642sets
643.Va errno
644to
645.Er EMLINK instead of
646.Er ELOOP
647as specified by
648.Tn POSIX
649when
650.Dv O_NOFOLLOW
651is set in flags and the final component of pathname is a symbolic link
652to distinguish it from the case of too many symbolic link traversals
653in one of its non-final components.
654.Sh HISTORY
655The
656.Fn open
657function appeared in
658.At v1 .
659The
660.Fn openat
661function was introduced in
662.Fx 8.0 .
663.Dv O_DSYNC
664appeared in 13.0.
665.Sh BUGS
666The Open Group Extended API Set 2 specification requires that the test
667for whether
668.Fa fd
669is searchable is based on whether
670.Fa fd
671is open for searching, not whether the underlying directory currently
672permits searches.
673The present implementation of the
674.Fa openat
675checks the current permissions of directory instead.
676.Pp
677The
678.Fa mode
679argument is variadic and may result in different calling conventions
680than might otherwise be expected.
681