musl - The musl libc tree (WIP / dev branches)

Age	Commit message (Collapse)	Author	Files	Lines
2022-05-01	only use getrlimit/setrlimit syscalls if they exist	Stefan O'Rear	1	-0/+6
	riscv32 and future architectures only provide prlimit64.
2020-10-27	avoid __synccall for setrlimit on kernels with prlimit syscall	Rich Felker	1	-20/+17
	resource limits have been process-wide since linux 2.6.10, and the prlimit syscall was added in 2.6.36, so prlimit can be assumed to set the resource limits correctly for the whole process.
2018-09-12	remove spurious inclusion of libc.h for LFS64 ABI aliases	Rich Felker	1	-1/+1
	the LFS64 macro was not self-documenting and barely saved any characters. simply use weak_alias directly so that it's clear what's being done, and doesn't depend on a header to provide a strange macro.
2018-09-12	remove or make static various unused __-prefixed symbols	Rich Felker	1	-1/+1

2015-01-15	for multithreaded set*id/setrlimit, handle case where callback does not run	Rich Felker	1	-3/+3
	in the current version of __synccall, the callback is always run, so failure to handle this case did not matter. however, the upcoming overhaul of __synccall will have failure cases, in which case the callback does not run and errno is already set. the changes being committed now are in preparation for that.
2014-05-30	fix for broken kernel side RLIM_INFINITY on mips	Szabolcs Nagy	1	-2/+10
	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).
2012-01-20	use prlimit syscall for getrlimit/setrlimit	Rich Felker	1	-1/+7
	this allows the full range of 64-bit limit arguments even on 32-bit systems. fallback to the old syscalls on old kernels that don't support prlimit.
2011-07-30	fix some bugs in setxid and update setrlimit to use __synccall	Rich Felker	1	-2/+27
	setrlimit is supposed to be per-process, not per-thread, but again linux gets it wrong. work around this in userspace. not only is it needed for correctness; setxid also depends on the resource limits for all threads being the same to avoid situations where temporarily unlimiting the limit succeeds in some threads but fails in others.
2011-03-20	global cleanup to use the new syscall interface	Rich Felker	1	-1/+1

2011-02-12	initial check-in, version 0.5.0v0.5.0	Rich Felker	1	-0/+11