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.

Description of problem:

The kvdo module fails to compile in kernel version 5.14.0-34, due to the symbols bvec_kmap_irq and bvec_kunmap_irq having been removed in backported code.

Version-Release number of selected component (if applicable):

kmod-kvdo 8.1.0.316-8.el9

How reproducible:

Steps to Reproduce:

1. Attempt to compile the kmod-kvdo kernel module

Actual results:

Compilation fails with missing symbol.

Expected results:

Compilation completes without warnings or failures.

Additional info:

The two patches applied in MR 20 [0] get us past the compilation failures, but then during testing another problem was found that causes a newly created VDO volume to panic the system when it tries to create kobjects.  That issue is due to a change [1] that was backported via BZ2018403.

In order to get a functional VDO back into operation, the plan is to temporarily remove all sysfs functionality while we work out the appropriate fix.  We know that there are things that depend on the sysfs functionality and I've reached out most of to those affected to confirm that it would be OK.  I've also tested that running a LVM-VDO volume without sysfs still works, despite missing the statistics needed for the 'lvs' output.

[0] https://gitlab.com/redhat/centos-stream/rpms/kmod-kvdo/-/merge_requests/20
[1] https://listman.redhat.com/archives/dm-devel/2021-August/msg00008.html

*** Bug 2039775 has been marked as a duplicate of this bug. ***

Verified with kmod-kvdo-8.1.1.287-12.el9

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 (new packages: kmod-kvdo), 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-2022:3919