canonical-ubuntu-qa team mailing list archive

[Manuel Diewald <2105376@xxxxxxxxxxxxxxxxxx>]

Fwiw, when the test is hanging, the two threads of the bind05 test
program are blocked in read() calls on the socket:

Thread 1:
#0  0x00007fd81e0323ad in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x0000000000406277 in read (__nbytes=127, __buf=0x7ffd3341fc50, __buf@entry=0x7ffd3341fa40, __fd=3, __fd@entry=127) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  safe_read (file=file@entry=0x421c1a "bind05.c", lineno=lineno@entry=162, cleanup_fn=cleanup_fn@entry=0x0, len_strict=len_strict@entry=0 '\000', fildes=fildes@entry=3, 
    buf=buf@entry=0x7ffd3341fc50, nbyte=nbyte@entry=127) at safe_macros.c:294
#3  0x0000000000405518 in test_bind (n=<optimized out>) at bind05.c:162
#4  0x000000000041280b in run_tests () at tst_test.c:1464
#5  testrun () at tst_test.c:1530
#6  fork_testrun () at tst_test.c:1659
#7  0x000000000041486a in tst_run_tcases (argc=<optimized out>, argv=<optimized out>, self=self@entry=0x633b20 <test>) at tst_test.c:1755
#8  0x000000000040508e in main (argc=<optimized out>, argv=<optimized out>) at ../../../../include/tst_test.h:414

Thread 2:
#0  0x00007fd81e0323ad in read () at ../sysdeps/unix/syscall-template.S:81
81	in ../sysdeps/unix/syscall-template.S
(gdb) bt
#0  0x00007fd81e0323ad in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x0000000000406277 in read (__nbytes=4, __buf=0x7fd81dc58efc, __buf@entry=0x7fd81dc58ebc, __fd=__fd@entry=4) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  safe_read (file=file@entry=0x421c1a "bind05.c", lineno=lineno@entry=103, cleanup_fn=cleanup_fn@entry=0x0, len_strict=len_strict@entry=1 '\001', fildes=fildes@entry=4, 
    buf=buf@entry=0x7fd81dc58efc, nbyte=nbyte@entry=4) at safe_macros.c:294
#3  0x0000000000405224 in peer_thread (tc_ptr=0x7ffd3341fb30) at bind05.c:103
#4  0x00007fd81e02b184 in start_thread (arg=0x7fd81dc59700) at pthread_create.c:312
#5  0x00007fd81dd5803d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2105376

Title:
  bind05 in ubuntu_ltp_syscalls fails consistently for trusty on
  openstack amd64 with lowlatency flavor

Status in ubuntu-kernel-tests:
  New

Bug description:
  In s2025.02.10 with trusty:linux 3.13.0-205.256,
  ubuntu_ltp_syscalls:bind05 started failing consistently across
  multiple runs on openstack amd64 for the lowlatency flavor. The
  generic flavor passes the test. In previous cycles, the test also
  passed for lowlatency. The test fails like this:

  Checking for required user/group ids

  'root' user id and group found.
  'nobody' user id and group found.
  'bin' user id and group found.
  'daemon' user id and group found.
  Users group found.
  Sys group found.
  Required users/groups exist.
  no big block device was specified on commandline.
  Tests which require a big block device are disabled.
  You can specify it with option -z
  INFO: Test start time: Wed Mar 26 07:14:13 UTC 2025
  COMMAND:    /opt/ltp/bin/ltp-pan -q  -e -S   -a 23308     -n 23308  -f /tmp/ltp-8wMYCG9xYV/alltests -l /dev/null  -C /dev/null -T /dev/null
  LOG File: /dev/null
  FAILED COMMAND File: /dev/null
  TCONF COMMAND File: /dev/null
  Running tests.......
  tst_test.c:1741: TINFO: LTP version: 20240129
  tst_test.c:1627: TINFO: Timeout per run is 0h 00m 30s
  bind05.c:131: TINFO: Testing AF_UNIX pathname datagram
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing AF_UNIX abstract datagram
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing IPv4 loop UDP variant 1
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing IPv4 loop UDP variant 2
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing IPv4 loop UDP-Lite
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing IPv4 any UDP variant 1
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing IPv4 any UDP variant 2
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing IPv4 any UDP-Lite
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing IPv6 loop UDP variant 1
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing IPv6 loop UDP variant 2
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing IPv6 loop UDP-Lite
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing IPv6 any UDP variant 1
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing IPv6 any UDP variant 2
  bind05.c:167: TPASS: Communication successful
  bind05.c:131: TINFO: Testing IPv6 any UDP-Lite
  Test timeouted, sending SIGKILL!
  tst_test.c:1680: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1
  tst_test.c:1681: TBROK: Test killed! (timeout?)

  Summary:
  passed   13
  failed   0
  broken   1
  skipped  0
  warnings 0

  The following commits have been added since the last version of the
  kernel that successfully completed the test:

  9b4da71fd0ae regmap: Fix possible double-free in regcache_rbtree_exit()
  b99f71817a70 jfs: add a check to prevent array-index-out-of-bounds in dbAdjTree
  1a9c06226ca9 ext4: fix memory leak in ext4_fill_super
  d04dc3f5c3f3 net: caif: fix memory leak in caif_device_notify
  2187acc04f18 net: caif: added cfserl_release function
  94d57c32abb7 net: caif: add proper error handling
  8a36766d357a net: inet6: do not leave a dangling sk pointer in inet6_create()
  f85d9710dd95 net: defer final 'struct net' free in netns dismantle

  If this turns out to be a regression, bisecting these should reveal
  the culprit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2105376/+subscriptions