Bug#762404: glibc: FTBFS[kfreebsd] tst-execstack fails; expected behaviour
Package: glibc
Version: 2.19.11
Severity: serious
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
Hi,
During a test rebuild for kfreebsd 10.1 transition, I noticed that glibc
fails to build from source already on kfreebsd 10.0:
Encountered regressions that don't match expected failures (debian/testsuite-checking/expected-results-x86_64-kfreebsd-gnu-libc):
tst-execstack-needed.out, Error 1
tst-execstack.out, Error 1
tst-execstack-prog.out, Error 1
TEST tst-execstack-needed.out:
DSO called ok (local 0x7fffffffd2b0, trampoline 0x7fffffffd2b1)
TEST tst-execstack.out:
executable stacks allowed
DSO called ok (local 0x7fffffffd290, trampoline 0x7fffffffd291)
executable stacks allowed
threads waiting
DSO called ok (local 0x7fffffffd200, trampoline 0x7fffffffd201)
Stack address remains the same: 0x7fffffffe000
TEST tst-execstack-prog.out:
DSO called ok (local 0x7fffffffd2c0, trampoline 0x7fffffffd2c1)
That shows kfreebsd-amd64; it fails similarly on kfreebsd-i386. This
is actually by design. The test program is killed due to a new default
setting of:
kern.elf64.nxstack: 1
kern.elf32.nxstack: 1
Similar to SElinux enforcement of allow_execstack=0 - something the
test program checks for and knows how to handle. So I suggest the test
could be fixed for any version of kfreebsd by checking the appropriate
sysctl.
The Debian buildds run a 9.0 kernel with nxstack=0 so are not affected
*yet*, but the package will start to FTBFS as soon as they are updated
to a jessie kernel, which would of course be a problem for future s-p-u
and jessie-security. (Hence the severity).
Thanks.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: kfreebsd-amd64 (x86_64)
Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Reply to: