timer_getoverrun01 from ubuntu_ltp_syscalls failed with J-5.15 openstack s390x

[Po-Hsu Lin]

Issue found with:
  * Jammy 5.15.0-102.112
  * Jammy 6.5.0-27.28~22.04.1
On openstack s390x instance. Note that we didn't run ubuntu_ltp_syscalls on manually provisioned s390x instances.

This can be reproduced with Jammy 5.15.0-100-generic. But Mantic 6.5.0-27.28 is OK.

Test log:
  INFO: Test start time: Wed Mar 20 07:58:53 UTC 2024
  COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 871640 -n 871640 -f /tmp/ltp-UfPg4uCVQO/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:1625: TINFO: Timeout per run is 0h 00m 30s
  timer_getoverrun01.c:35: TFAIL: tst_syscall(__NR_timer_getoverrun, timer) failed: EINVAL (22)
  timer_getoverrun01.c:38: TBROK: timer_delete() failed: EINVAL (22)

  Summary:
  passed 0
  failed 1
  broken 1
  skipped 0
  warnings 0
  INFO: ltp-pan reported some tests FAIL
  LTP Version: 20240129
  INFO: Test end time: Wed Mar 20 07:58:53 UTC 2024

After some investigation, it seems that this might be a test case issue with recent LTP fork update.
Bisect shows
31b98805831743d663bb2dd67822d9fcbd538884 is the first bad commit
commit 31b98805831743d663bb2dd67822d9fcbd538884
Author: Andrea Cervesato <email address hidden>
Date: Thu Nov 16 16:21:08 2023 +0100

    Refactor timer_getoverrun test using new LTP API

    Link: https://<email address hidden>/
    Reviewed-by: Richard Palethorpe <email address hidden>
    Reviewed-by: Cyril Hrubis <email address hidden>
    Reviewed-by: Petr Vorel <email address hidden>
    Signed-off-by: Andrea Cervesato <email address hidden>

 .../syscalls/timer_getoverrun/timer_getoverrun01.c | 105 ++++++---------------
 1 file changed, 31 insertions(+), 74 deletions(-)