bash 5.2 regression too-aggressive optimizing of forks in an `eval' command inside a (command) subshell
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bash (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| ovn (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
OVN makes use of GNU autotest for its testsuite. This in turn is a heavy user of bash.
For some reason, when the 'ovn-controller incremental processing' test is executed using bash 5.2 on Debian experimental or Ubuntu Kinetic/Lunar, the `eval` [0] in the `counter_delta_` function misinterprets successful execution of commands [1], leading to a false negative for the 'ovn-controller incremental processing' test [2].
Backporting the bash 5.1 package from Jammy, or compiling bash 5.1 from upstream sources and rerunning the test makes it succeed.
This does come across as a regression in bash.
0: https:/
1: https:/
2: https:/
| description: | updated |
| description: | updated |
| summary: |
- The `ovn-controller incremental processing` test fails when bash 5.2 is - installed + bash 5.2 regression in optimize_connection_fork |
| Frode Nordahl (fnordahl) wrote Re: bash 5.2 regression in optimize_connection_fork | #1 |
| Frode Nordahl (fnordahl) wrote | #2 |
| summary: |
- bash 5.2 regression in optimize_connection_fork + bash 5.2 regression too-aggressive optimizing of forks in an `eval' + command inside a (command) subshell |
| Frode Nordahl (fnordahl) wrote | #3 |
| Frode Nordahl (fnordahl) wrote | #4 |
| Changed in bash (Ubuntu): | |
| status: | New → Fix Committed |
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in ovn (Ubuntu): | |
| status: | New → Fix Released |
| Changed in bash (Ubuntu): | |
| status: | Fix Committed → Fix Released |
https:/