summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorSzabolcs Nagy <nsz@port70.net>2014-05-30 08:47:35 +0200
committerRich Felker <dalias@aerifal.cx>2014-05-30 03:09:26 -0400
commit8258014fd1e34e942a549c88c7e022a00445c352 (patch)
tree4e02c1ef57223e02a42194c435f9b566347d0cb1 /arch
parent106e65d6f6ba4d027e1fde1b1d2fabb92714da94 (diff)
downloadmusl-8258014fd1e34e942a549c88c7e022a00445c352.tar.gz
musl-8258014fd1e34e942a549c88c7e022a00445c352.tar.bz2
musl-8258014fd1e34e942a549c88c7e022a00445c352.tar.xz
musl-8258014fd1e34e942a549c88c7e022a00445c352.zip
fix for broken kernel side RLIM_INFINITY on mips
On 32 bit mips the kernel uses -1UL/2 to mark RLIM_INFINITY (and this is the definition in the userspace api), but since it is in the middle of the valid range of limits and limits are often compared with relational operators, various kernel side logic is broken if larger than -1UL/2 limits are used. So we truncate the limits to -1UL/2 in get/setrlimit and prlimit. Even if the kernel side logic consistently treated -1UL/2 as greater than any other limit value, there wouldn't be any clean workaround that allowed using large limits: * using -1UL/2 as RLIM_INFINITY in userspace would mean different infinity value for get/setrlimt and prlimit (where infinity is always -1ULL) and userspace logic could break easily (just like the kernel is broken now) and more special case code would be needed for mips. * translating -1UL/2 kernel side value to -1ULL in userspace would mean that -1UL/2 limit cannot be set (eg. -1UL/2+1 had to be passed to the kernel instead).
Diffstat (limited to 'arch')
-rw-r--r--arch/mips/syscall_arch.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/arch/mips/syscall_arch.h b/arch/mips/syscall_arch.h
index c52976eb..e62c3398 100644
--- a/arch/mips/syscall_arch.h
+++ b/arch/mips/syscall_arch.h
@@ -5,6 +5,8 @@
long (__syscall)(long, ...);
+#define SYSCALL_RLIM_INFINITY (-1UL/2)
+
#ifndef __clang__
#define __asm_syscall(...) do { \