Re: [bug-bash] The kill test of util-linux fails with bash 5.3
From:
Dr. Werner Fink
Subject:
Re: [bug-bash] The kill test of util-linux fails with bash 5.3
Date:
Tue, 22 Jul 2025 13:15:38 +0200
On 2025/07/22 10:33:41 +0100, Sam James wrote:
> "Dr. Werner Fink" <werner@suse.de> writes:
>
> > On 2025/07/22 09:08:38 +0200, werner@suse.de wrote:
> >> Configuration Information [Automatically generated, do not change]:
> >> Machine: x86_64
> >> OS: linux-gnu
> >> Compiler: gcc
> >> Compilation CFLAGS: -O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3
> >> -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables
> >> -fstack-clash-protection -Werror=return-type -flto=auto -g -D_GNU_SOURCE
> >> -DRECYCLES_PIDS -Wall -g -Wuninitialized -Wextra -Wno-switch-enum
> >> -Wno-unused-variable -Wno-unused-parameter -Wno-parentheses
> >> -ftree-loop-linear -pipe -DBNC382214=0 -DIMPORT_FUNCTIONS_DEF=0
> >> -DDEFAULT_LOADABLE_BUILTINS_PATH='/usr/lib64/bash'
> >> uname output: Linux noether 6.11.8-1-default #1 SMP PREEMPT_DYNAMIC Thu
> >> Nov 14 12:54:01 UTC 2024 (099023b) x86_64 x86_64 x86_64 GNU/Linux
> >> Machine Type: x86_64-suse-linux-gnu
> >>
> >> Bash Version: 5.3
> >> Patch Level: 0
> >> Release Status: release
> >>
> >> Description:
> >> The kill test of util-linux fails with bash 5.3
> >>
>
> I'd seen this but assumed it was actually an issue in the util-linux
> test.
OK it is easy to add the missing INT in the expected ignored signals for 5.4
>
> >
> > get_original_signal (SIGQUIT);
> > set_signal_handler (SIGQUIT, SIG_IGN);
> >
> > with the disabled line it works.
> >
> > Beside this I face some reports more from QA:
> > libssh has 32 tests failed out of 76 and qemu shows 3 failing tests.
>
> I suspect those aren't related. I at least didn't hit them.
At least this code in libssh fails in libssh-0.11.2/tests/torture.c line 1189
rc = snprintf(sshd_start_cmd,
sizeof(sshd_start_cmd),
"%s " SSHD_EXECUTABLE
" -r -f %s -E %s/sshd/daemon.log 2> %s/sshd/cwrap.log",
kdc_env,
s->srv_config,
s->socket_dir,
s->socket_dir);
if (rc < 0 || rc >= (int)sizeof(sshd_start_cmd)) {
fail_msg("snprintf failed");
}
rc = system(sshd_start_cmd);
assert_return_code(rc, errno);
unsetenv("NSS_WRAPPER_HOSTNAME");
setenv("SOCKET_WRAPPER_DEFAULT_IFACE", "21", 1);
unsetenv("PAM_WRAPPER");
/* Wait until the sshd is ready to accept connections */
rc = torture_wait_for_daemon(15);
assert_int_equal(rc, 0);
in the last assert as rc is 1 and I see a lot of
Connection failed : Failed to connect: No route to host
Tested in a KVM build environment with 5.3
--
"Having a smoking section in a restaurant is like having
a peeing section in a swimming pool." -- Edward Burr