mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-12-20 09:34:44 +08:00
c3525940cc
Currently on powerpc we have our own #define for the highest (negative) errno value, called _LAST_ERRNO. This is defined to be 516, for reasons which are not clear. The generic code, and x86, use MAX_ERRNO, which is defined to be 4095. In particular seccomp uses MAX_ERRNO to restrict the value that a seccomp filter can return. Currently with the mismatch between _LAST_ERRNO and MAX_ERRNO, a seccomp tracer wanting to return 600, expecting it to be seen as an error, would instead find on powerpc that userspace sees a successful syscall with a return value of 600. To avoid this inconsistency, switch powerpc to use MAX_ERRNO. We are somewhat confident that generic syscalls that can return a non-error value above negative MAX_ERRNO have already been updated to use force_successful_syscall_return(). I have also checked all the powerpc specific syscalls, and believe that none of them expect to return a non-error value between -MAX_ERRNO and -516. So this change should be safe ... Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Reviewed-by: Kees Cook <keescook@chromium.org> |
||
---|---|---|
.. | ||
auxvec.h | ||
bitsperlong.h | ||
bootx.h | ||
byteorder.h | ||
cputable.h | ||
eeh.h | ||
elf.h | ||
epapr_hcalls.h | ||
errno.h | ||
fcntl.h | ||
ioctl.h | ||
ioctls.h | ||
ipcbuf.h | ||
Kbuild | ||
kvm_para.h | ||
kvm.h | ||
mman.h | ||
msgbuf.h | ||
nvram.h | ||
opal-prd.h | ||
param.h | ||
perf_event.h | ||
poll.h | ||
posix_types.h | ||
ps3fb.h | ||
ptrace.h | ||
resource.h | ||
sembuf.h | ||
setup.h | ||
shmbuf.h | ||
sigcontext.h | ||
siginfo.h | ||
signal.h | ||
socket.h | ||
sockios.h | ||
spu_info.h | ||
stat.h | ||
statfs.h | ||
swab.h | ||
termbits.h | ||
termios.h | ||
tm.h | ||
types.h | ||
ucontext.h | ||
unistd.h |