Removing test case two, ulimit(UL_SETFSIZE, -1) since it is an invalid
test case. As stated in a recent message to the list:
From: Andreas Jaeger <aj@suse.de>
Ulrich Drepper mentioned:
> this specific problem is actually unspecified in the
> standard since it's not overflowing in rlim_t) we have to handle
> negative values appropriately. The problem is that some 32bit
> architectures support 4GB files and we simply have to ignore that the
> ulimit() result is signed. So, the compuations are carried out as if
> unsigned and on overflow RLIM_INFINITY is used.
glibc 2.2.5 will therefore not return a failure if ulimit (2, -1) is
run as root - or if RLIM_INFINITY was used before.
glibcs before 2.2.4 did not handle the overflow at all.
1 file changed