summaryrefslogtreecommitdiff
path: root/arch/arm/bits/fcntl.h
AgeCommit message (Collapse)AuthorLines
2015-04-01move O_PATH definition back to arch bitsRich Felker-0/+1
while it's the same for all presently supported archs, it differs at least on sparc, and conceptually it's no less arch-specific than the other O_* macros. O_SEARCH and O_EXEC are still defined in terms of O_PATH in the main fcntl.h.
2013-11-23add O_TMPFILE flag, new in linux 3.11Szabolcs Nagy-0/+1
definition in linux: #define O_TMPFILE (__O_TMPFILE | O_DIRECTORY) where __O_TMPFILE and O_DIRECTORY are arch specific
2013-01-12add missing F_GETOWNER_UIDS flag to bits/fcntl.hSzabolcs Nagy-0/+2
2012-11-18fcntl.h: O_SEARCH was missing for powerpcrofl0r-3/+0
put some macros that do not differ between architectures in the main header and remove from bits. restructure mips header so it has the same structure as the others.
2012-09-15add O_EXEC open modeRich Felker-0/+1
the linux O_PATH mode provides the necessary semantics for both the O_SEARCH and O_EXEC modes defined and required by POSIX 2008.
2012-09-13add O_PATH/O_SEARCH support to fcntl.hRich Felker-0/+2
I'm not 100% sure that Linux's O_PATH meets the POSIX requirements for O_SEARCH, but it seems very close if not perfect. and old kernels ignore it, so O_SEARCH will still work as desired as long as the caller has read permissions to the directory.
2012-06-20proper error handling for fcntl F_GETOWN on modern kernelsRich Felker-0/+3
on old kernels, there's no way to detect errors; we must assume negative syscall return values are pgrp ids. but if the F_GETOWN_EX fcntl works, we can get a reliable answer.
2012-04-15move F_DUPFD_CLOEXEC out of bitsRich Felker-2/+0
fcntl values 1024 and up are universal, arch-independent. later I'll add some of the other linux-specific ones for notify, leases, pipe size, etc. here too.
2012-04-15add F_SETSIG and F_GETSIG (linux specific) to fcntl.hRich Felker-0/+2
F_* is in the reserved namespace so no feature test is needed
2011-10-05fix fcntl O_* flags for armRich Felker-4/+4
no idea why these 4 are permuted and the rest are standard/generic
2011-09-18initial commit of the arm portRich Felker-0/+33
this port assumes eabi calling conventions, eabi linux syscall convention, and presence of the kernel helpers at 0xffff0f?0 needed for threads support. otherwise it makes very few assumptions, and the code should work even on armv4 without thumb support, as well as on systems with thumb interworking. the bits headers declare this a little endian system, but as far as i can tell the code should work equally well on big endian. some small details are probably broken; so far, testing has been limited to qemu/aboriginal linux.