EFAULT
Bad address
- Linux value
- 14
- strerror(3)
- Bad address
- On this site
- 14 syscalls
A pointer argument points outside the address space you can use.
Where you will see EFAULT
- cachestat(2)Linux · Filesystem
cstat_range or cstat is not a valid user address.
- capset(2)Linux · Security
Bad memory address; hdrp must not be NULL.
- fsopen(2)Linux · Filesystem
fsopen(): fsname is NULL or points outside the accessible address space.
- futex(2)Linux · IPC
uaddr (or timeout) did not point to a valid user-space address.
- getrandom(2)Linux · Security
buf points outside the accessible address space.
- landlock_create_ruleset(2)Linux · Sandboxing
attr is not a valid address.
- memfd_create(2)Linux · Memory
name points to invalid memory.
- pledge(2)OpenBSD · Sandboxing
promises or execpromises points outside the process's address space.
- prctl(2)Linux · Processes
A pointer argument (e.g. a seccomp filter) is an invalid address.
- process_madvise(2)Linux · Memory
iovec describes memory outside the target's accessible address space.
- process_vm_readv(2)Linux · Memory
A range in local_iov is not mapped in the caller's address space.
- rseq(2)Linux · Scheduling
rseq pointer is NULL or not readable/writable by the process.
- sched_setaffinity(2)Linux · Processes
A supplied memory address was invalid.
- seccomp(2)Linux · Sandboxing
args was not a valid address.
Sources
- errno(3), Linux man-pages
- The meaning for each syscall is taken from that syscall's own card and the man page it cites.
Values are the Linux numbers on x86 and arm64; other architectures and the BSDs number some errors differently. BSD cards list the names the BSD man page uses. Spot one that's wrong? Tell Rod.