That's right, it was a fix for a Virtualbox error that arose when kernel stack randomization was first introduced in the 5.13 kernel. My speculation was that it might have been a similar issue, and if so, its fix might give a clue to a way to fix the current issue in Virtualbox.
One might naively observe that when the available kernel stack space was reduced by 0.25kb in kernel 5.13, Virtualbox was fixed by adding 256 to STACK_FUZZ_SIZE. Now kernel 5.15.0-116 has reduced the available stack space by another 0.75kb; could Virtualbox be fixed by adding another 768 to STACK_FUZZ_SIZE? I don't know enough about what's going on under the hood to know if that's even plausible, or what undesirable side effects it might have. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
