Bug#886974: [Debian-ha-maintainers] Bug#886974: kronosnet: FTBFS on x32: api_knet_send_crypto_test segmentation fault

[Aaron M. Ucko]

Ferenc Wágner  writes:

> I've been looking into this for quite some time.

Great, thanks!

> I created an x32 build environment, and the build finished without any
> problem, I failed to reproduce the segfault.  If you could extract a
> core dump or at least a backtrace from the buildd, I'd gladly check it
> out.

To be clear, I'm not a porter or buildd maintainer, just a regular DD
who's found that architecture-specific build failures sometimes slip
through the cracks and likes to help ensure they don't.  It looks like
valgrind doesn't yet support x32, but I suppose you could see if
building with -fsanitize=address catches anything.  (Also, I'm not sure
autobuilders retain any details they don't publish anyway.)

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#886974: [Debian-ha-maintainers] Bug#886974: kronosnet: FTBFS on x32: api_knet_send_crypto_test segmentation fault

[Ferenc Wágner]

"Aaron M. Ucko"  writes:

> The build of kronosnet for x32 (admittedly not a release architecture)
> ran into errors in api_knet_send_crypto_test per the below excerpts from
> https://buildd.debian.org/status/fetch.php?pkg=kronosnet=x32=1.0-1=1515554249=0
>
> Could you please take a look?

> FAIL: api_knet_send_crypto_test
> ===
>
> Using port 3419
> [knet]: [ERROR] transport: Failed to set socket buffer via force option 33: 
> Operation not permitted
> [knet]: [ERROR] transport: Unable to set local socketpair receive buffer: 
> File name too long
> [knet]: [ERROR] transport: DEBIAN_SPECIFIC_KRONOSNET_TEST_MODE is set, 
> continuing regardless
> [knet]: [ERROR] transport: Failed to set socket buffer via force option 32: 
> Operation not permitted
> [knet]: [ERROR] transport: Unable to set local socketpair receive buffer: 
> File name too long
> [knet]: [ERROR] transport: DEBIAN_SPECIFIC_KRONOSNET_TEST_MODE is set, 
> continuing regardless
> [knet]: [ERROR] transport: Failed to set socket buffer via force option 33: 
> Operation not permitted
> [...]
> [knet]: [ERROR] transport: Failed to set socket buffer via force option 33: 
> Operation not permittFAIL api_knet_send_crypto_test (exit status: 139)

Hi Aaron,

I've been looking into this for quite some time.  I created an x32 build
environment, and the build finished without any problem, I failed to
reproduce the segfault.  If you could extract a core dump or at least a
backtrace from the buildd, I'd gladly check it out.
-- 
Regards,
Feri

Bug#886974: kronosnet: FTBFS on x32: api_knet_send_crypto_test segmentation fault

[Aaron M. Ucko]

Source: kronosnet
Version: 1.0-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: debian-...@lists.debian.org
Usertags: x32

The build of kronosnet for x32 (admittedly not a release architecture)
ran into errors in api_knet_send_crypto_test per the below excerpts from
https://buildd.debian.org/status/fetch.php?pkg=kronosnet=x32=1.0-1=1515554249=0

Could you please take a look?

Thanks!

--

../../test-driver: line 107:  3419 Segmentation fault  "$@" > $log_file 2>&1
FAIL: api_knet_send_crypto_test
[...]
# TOTAL: 62
# PASS:  61
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: api_knet_send_crypto_test
===

Using port 3419
[knet]: [ERROR] transport: Failed to set socket buffer via force option 33: 
Operation not permitted
[knet]: [ERROR] transport: Unable to set local socketpair receive buffer: File 
name too long
[knet]: [ERROR] transport: DEBIAN_SPECIFIC_KRONOSNET_TEST_MODE is set, 
continuing regardless
[knet]: [ERROR] transport: Failed to set socket buffer via force option 32: 
Operation not permitted
[knet]: [ERROR] transport: Unable to set local socketpair receive buffer: File 
name too long
[knet]: [ERROR] transport: DEBIAN_SPECIFIC_KRONOSNET_TEST_MODE is set, 
continuing regardless
[knet]: [ERROR] transport: Failed to set socket buffer via force option 33: 
Operation not permitted
[...]
[knet]: [ERROR] transport: Failed to set socket buffer via force option 33: 
Operation not permittFAIL api_knet_send_crypto_test (exit status: 139)

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu