Bug 2119819
| Summary: | Latest kmod-kvdo does not work with latest RHEL-8.8.0 kernel | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | RHEL Program Management Team <pgm-rhel-tools> | |
| Component: | kmod-kvdo | Assignee: | Andy Walsh <awalsh> | |
| Status: | CLOSED ERRATA | QA Contact: | Filip Suba <fsuba> | |
| Severity: | unspecified | Docs Contact: | Apurva Bhide <abhide> | |
| Priority: | unspecified | |||
| Version: | 8.7 | CC: | abhide, awalsh, cwei, fsuba, lmiksik, pasik, slegendr | |
| Target Milestone: | rc | Keywords: | Triaged | |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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.
|
Story Points: | --- | |
| Clone Of: | 2060475 | |||
| : | 2173037 (view as bug list) | Environment: | ||
| Last Closed: | 2023-05-16 09:03:20 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 2060475 | |||
| Bug Blocks: | 2173037 | |||
|
Description
RHEL Program Management Team
2022-08-19 13:47:47 UTC
Verified that kmod-kvdo-6.2.8.7-88.el8 works with latest kernel. 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 |