Preparing for the next release: call for testing

[Dmitry V. Levin]

On Thu, Dec 10, 2015 at 09:37:35PM -0500, Mike Frysinger wrote:
> i haven't had a chance yet to triage these.
> 
> testing commit bab4ef4272cd2596c7390b34ea8acc086ee8fdb2 (v4.10-566-gbab4ef4)
> 
> native (build+tests):
> vFAIL:  build;  x86_64  ???         linux-4.1.6         kernel-headers-3.4.0   glibc-2.4   gcc-4.5.4
> vFAIL:  build;  sparc64  ???  cross  kernel-headers-4.3.0  glibc-2.22  gcc-4.6.4
> ./mpers.sh: line 21: 18442 Killed                  gawk -v VAR_NAME="$VAR_NAME" -v ARCH_FLAG="${ARCH_FLAG#-}" -f "$MPERS_AWK" "${f_d2}" > "${f_h}"

Was it an OOM killer in both cases?

> vFAIL:  test;   armv7l  32-bit/LSB  linux-3.4.0-vapier  kernel-headers-3.18.0  glibc-2.21  gcc-4.9.3
> Segmentation fault
> inet-cmsg.test: failed test: ./inet-cmsg failed

tests/inet-cmsg.c sagfaulted, need more info.

> FAIL: restart_syscall
> nanosleep({0, 222222222}, {0, 112075472}) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
> --- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} ---
> nanosleep(0xfffffffc, 0x7e97b108) = 0

The last nanosleep line should look this way:
nanosleep({0, 222222222}, 0x7e97b108) = 0
0xfffffffc is not a valid pointer to struct timespec, it's -EINTR!
Has the kernel corrupted ARM_r0 in do_signal?

> vFAIL:  test;   x86_64  32-bit/LSB  linux-4.1.6         kernel-headers-4.1.0   glibc-2.21  gcc-4.9.2
> < times({tms_utime=22, tms_stime=17, tms_cutime=33, tms_cstime=26}) = 18446744071580810102
> ---
> > times({tms_utime=22, tms_stime=17, tms_cutime=33, tms_cstime=26}) = 2166225782

Looks like a sign extension bug in libc.
Is there any safe way on x32 to call times(2) directly?


-- 
ldv
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20151211/2ae42825/attachment.bin>