Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This is a preliminary list of vsock fixes we have in Linux 6.1-rc3 that we should backport into RHEL-8.8:

7a4efe182ca6 vhost/vsock: Fix error handling in vhost_vsock_init()
7e97cfed9929 vsock: Fix memory leak in vsock_connect()
a3e7b29e3085 vsock: Set socket state back to SS_UNCONNECTED in vsock_connect_timeout()
0e3f72931fc4 vhost/vsock: Use kvmalloc/kvfree for larger packets.
44aa5a6dba82 net: vmw_vsock: vmci: Check memcpy_from_msg()

Updated the result from Virt QE team - RHEL in ESXi.


Tested with 4.18.0-448.el8.4081_744511162.g8ec2 and passed the regression.


Test Environment
    Host: ESXi 7.0
    Guest: RHEL-8.8.0 with 4.18.0-448.el8.4081_744511162.g8ec2


Steps to Test
0. Upgraded the Guest with Repo URL based on above target Host.
1. Launched its regression with CI - https://ci-jenkins-csb-esxi.apps.ocp-c1.prod.psi.redhat.com/job/ESXi-Project/job/regression-trigger/30/, and checked cases status if failed.


If you have any specific cases or steps to try, let me know.

Pre-verified on rhel 8.8

kernel: 4.18.0-448.el8.4081_744511162.g8ec2.x86_64
qemu: qemu-kvm-6.2.0-28.module+el8.8.0+17721+63bacee8.x86_64

Vsock regression test PASS.

Verified on rhel 8.8

kernel: 4.18.0-452.el8.x86_64
qemu-kvm: qemu-kvm-6.2.0-28.module+el8.8.0+17721+63bacee8.x86_64

Vsock automation tests PASS.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: kernel security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:2951