On Sun, Dec 10, 2023 at 11:05:37PM -0500, Simon Kaegi wrote: > #regzbot introduced v6.1.62..v6.1.63 > #regzbot introduced: baddcc2c71572968cdaeee1c4ab3dc0ad90fa765 > > We hit this regression when updating our guest vm kernel from 6.1.62 to > 6.1.63 -- bisecting, this problem was introduced > in baddcc2c71572968cdaeee1c4ab3dc0ad90fa765 -- virtio/vsock: replace > virtio_vsock_pkt with sk_buff -- > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.63&id=baddcc2c71572968cdaeee1c4ab3dc0ad90fa765 > > We're getting a timeout when trying to connect to the vsocket in the > guest VM when launching a kata containers 3.2.0 agent. We haven't done > much more to understand the problem at this point. > > We can reproduce 100% of the time but don't currently have a simple > reproducer as the problem was found in our build service which uses > kata-containers (with cloud-hypervisor). > > We have not checked the mainline as we currently are tied to 6.1.x. What is "tieing" you to the old 6.1.y tree? Also, can you try 6.1.66? Numerous fixes have gone into there as well. thanks, greg k-h
