Public bug reported: - Problem Descripion: Kernel 4.19 introduced a bug in the Vsock protocol when using a large Context ID.
E.g. CID 0xfff000 works correctly but CID 0xfff001 fails with ENODEV when trying to connect to the listener. The issue now also shows up in Ubuntu 18.04 with -> kernel 4.15.0-44-generic #47-Ubuntu on x86_64 and s390x. It is already fixed upstream kernel by: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7fbe078c37aba3088359c9256c1a1d0c3e39ee81 ** Affects: ubuntu-z-systems Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-175098 severity-high targetmilestone-inin1804 ** Tags added: architecture-s39064 bugnameltc-175098 severity-high targetmilestone-inin1804 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813934 Title: Vsock connect fails with ENODEV for large CID To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1813934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
