setrlimit01: caught SIGTERM as well

Caught SIGTERM to avoid TBROK like:

setrlimit01    1  TPASS  :  RLIMIT_NOFILE functionality is correct
setrlimit01    2  TPASS  :  RLIMIT_FSIZE test PASSED
setrlimit01    3  TPASS  :  RLIMIT_NPROC functionality is correct
setrlimit01    4  TPASS  :  RLIMIT_CORE functionality is correct
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=0 corefile=no
cutime=0 cstime=0
<<<test_end>>>
setrlimit01    3  TBROK  :  caught unexpected signal: 15
setrlimit01    4  TBROK  :  Remaining cases broken

Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
get_robust_list01: use pid_max instead of UINT16_MAX

UINT16_MAX can be a valid pid number on some systems.

Signed-off-by: Jan Stancek <jstancek@redhat.com>
Reviewed-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
semop/semop04.c: fix a bug when running with -i option

If we run semop04 like this: ./semop04 -i 2,
its output will be:

semop04     1  TPASS  :  expected failure - errno = 11 : Resource temporarily unavailable
semop04     2  TPASS  :  expected failure - errno = 11 : Resource temporarily unavailable
semop04     1  TBROK  :  semctl() failed
semop04     2  TBROK  :  Remaining cases broken.

Actually in the second iteration, semctl will return ERANGE. This is
because the val variable will be less than zero in the sceond iteration.

Variable val should be reset to 1 before this actual errno test.

Signed-off-by: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
Reviewed-by: Jan Stancek <jstancek@redhat.com>
Reviewed-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>