jonasalfredsson / bash_fail-to-wait Goto Github PK

Here is the result on kernel 5.12.3

No error on run50

$ make run50
docker run -it --rm --name waiter wait-reproducer bash5.0 ./fail_to_wait.sh

GNU bash, version 5.0.3(1)-release (x86_64-pc-linux-gnu)

A child process with PID 10 has now started
loop_iteration: 0
Pre signal code: 
Received SIGHUP
Post signal code: 129
loop_iteration: 1
Pre signal code: 129

Error on run51

$ make run51
docker run -it --rm --name waiter wait-reproducer bash5.1 ./fail_to_wait.sh

GNU bash, version 5.1.0(1)-release (x86_64-pc-linux-gnu)

A child process with PID 10 has now started
loop_iteration: 0
Pre signal code: 
Received SIGHUP
Post signal code: 129
loop_iteration: 1
Pre signal code: 129
Post signal code: 127
make: *** [Makefile:14: run51] Error 127

Error on bash 5.1 and not on bash 5.0 . I am able to reproduce it on my end.

I reported this issue to [email protected], and got a response from Chet Ramey who agreed with me that this was a regression.

Thanks for the report. The issue is a change between bash-5.0 and bash-5.1
to understand PID arguments with -n. The job state wasn't restored upon
receipt of all trapped signals and interfered with subsequent calls to
`wait -n'.

Chet

He was also extremely quick in providing a patch, which I will attach here as well.

I have not heard anything about when this fix will be released, but I guess it will be included in the next version.

wait-n-reset.patch.txt