pty07 from ubuntu_ltp cause VM crash with N-oem-6.10

[Po-Hsu Lin]

The pty07 test from ubuntu_ltp will cause test interrupt with Noble OEM 6.10 VM on openstack since 6.10.0-1003.3

This issue can be reproduced with a VM on a bare-metal. When this happens the VM will be terminated. (Test passed on a Bare-metal with 6.10.0-1005-oem).

Test log:
<<<test_start>>>
tag=pty07 stime=1719989938
cmdline="pty07"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1733: TINFO: LTP version: 20230929-609-g3fc2d1b15
tst_test.c:1617: TINFO: Timeout per run is 0h 03m 00s
pty07.c:92: TINFO: Saving active console 1
(VM terminated here)

Steps:
# On a bare-metal running with Noble
sudo apt install uvtool build-essential -y
sudo uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily release=noble arch=amd64
SSH_KEY="$HOME/.ssh/id_rsa"
ssh-keygen -f $SSH_KEY -t rsa -N ''
sudo -u ubuntu uvt-kvm create oem610 release=noble arch=amd64 --memory 2048
sleep 60
ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -i .ssh/id_rsa ubuntu@`sudo uvt-kvm ip oem610`
# Inside the VM
sudo apt-add-repository ppa:canonical-kernel-team/ubuntu/proposed -y
sudo apt install kernel-testing--linux-oem-6.10--full--oem -y
sudo reboot
sleep 60
ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -i .ssh/id_rsa ubuntu@`sudo uvt-kvm ip oem610`
git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests -b build-only
git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest -b autotest3
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_ltp/control
echo "pty07 pty07" > /home/ubuntu/pty
sudo /opt/ltp/runltp -f /home/ubuntu/pty

This issue can be reproduced with mainline kernel v6.10-rc4 (AMD64 debs are not available for v6.10-rc6)

[Po-Hsu Lin (cypressyew)]

This issue can be found with Oracular 6.10.0-4.4 AMD64 openstack instance as well.