Thanks for taking the time to report the bug and make Ubuntu better.
I can reproduce the bug using your testcase, but that requires a VM with a graphical environment installed. Another way to reproduce the bug is (from the upstream bug report):
$ lxc launch ubuntu-daily:jammy ssh-cpu $ lxc shell ssh-cpu # ssh HOST 2> >({exec 1>&2})
You can shell into the container from another terminal and use "htop" to verify that ssh is using 100% of one of the CPU cores.
This seems to have been fixed upstream by the following commit:
https://github.com/openssh/openssh-portable/commit/d6556de1db0822c76ba2745cf5c097d9472adf7c
I confirmed that this only happens on Jammy. Focal and Kinetic are not affected.
Thanks for taking the time to report the bug and make Ubuntu better.
I can reproduce the bug using your testcase, but that requires a VM with a graphical environment installed. Another way to reproduce the bug is (from the upstream bug report):
$ lxc launch ubuntu-daily:jammy ssh-cpu
$ lxc shell ssh-cpu
# ssh HOST 2> >({exec 1>&2})
You can shell into the container from another terminal and use "htop" to verify that ssh is using 100% of one of the CPU cores.
This seems to have been fixed upstream by the following commit:
https:/ /github. com/openssh/ openssh- portable/ commit/ d6556de1db0822c 76ba2745cf5c097 d9472adf7c
I confirmed that this only happens on Jammy. Focal and Kinetic are not affected.