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.
Bug 2119819 - Latest kmod-kvdo does not work with latest RHEL-8.8.0 kernel
Summary: Latest kmod-kvdo does not work with latest RHEL-8.8.0 kernel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kmod-kvdo
Version: 8.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Andy Walsh
QA Contact: Filip Suba
Apurva Bhide
URL:
Whiteboard:
Depends On: 2060475
Blocks: 2173037
TreeView+ depends on / blocked
 
Reported: 2022-08-19 13:47 UTC by RHEL Program Management Team
Modified: 2023-05-16 19:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
.System works correctly without the soft lockup while starting a VDO volume Due to fixing a Kernel Application Binary Interface (kABI) bug in the `pv_mmu_ops` structure, RHEL 8.7 systems with kernel version `4.18.0-425.10.1.el8_7`, that is RHEL-8.7.0.2-BaseOS, hung or encountered a kernel panic due to soft lockup while starting a Virtual Data Optimizer (VDO) volume. With this update, the `kmod-kvdo` package was rebuilt any time a new kernel was available that is no longer kABI compatible with the current version of `kmod-kvdo`. As a result, the system works correctly while starting a VDO volume.
Clone Of: 2060475
: 2173037 (view as bug list)
Environment:
Last Closed: 2023-05-16 09:03:20 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-131750 0 None None None 2022-08-19 13:53:31 UTC
Red Hat Product Errata RHBA-2023:2957 0 None None None 2023-05-16 09:03:28 UTC

Description RHEL Program Management Team 2022-08-19 13:47:47 UTC 
Description of problem:
This is a placeholder bug to handle rebuilds of kmod-kvdo any time a new kernel is available that is no longer kABI compatible with the current version of kmod-kvdo.

A previous example of this bug can be found at BZ2060475.

Steps to Reproduce:
1. Install RHEL-8.8.0
2. Install package versions referenced (kernel and kmod-kvdo)
3. Attempt to run `modprobe uds` or `modprobe kvdo`.

Expected results:
Modules loaded
Comment 12 Filip Suba 2023-04-06 07:46:03 UTC 
Verified that kmod-kvdo-6.2.8.7-88.el8 works with latest kernel.
Comment 14 errata-xmlrpc 2023-05-16 09:03:20 UTC 
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 (kmod-kvdo 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/RHBA-2023:2957
Note You need to log in before you can comment on or make changes to this bug.