Bug 2035003

Summary:	VDO compilation error under kernel 5.14.0-34
Product:	Red Hat Enterprise Linux 9	Reporter:	Joseph Chapman <jochapma>
Component:	kmod-kvdo	Assignee:	Andy Walsh <awalsh>
Status:	CLOSED ERRATA	QA Contact:	Filip Suba <fsuba>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	awalsh, bstinson, cwei, fsuba, guazhang, jwboyer, tbzatek, vtrefny
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	kmod-kvdo-8.1.1.360-12.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 15:49:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joseph Chapman 2021-12-22 17:09:27 UTC

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:

Comment 4 Andy Walsh 2022-01-05 15:30:40 UTC

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

Comment 6 Vojtech Trefny 2022-01-13 12:32:54 UTC

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

Comment 10 Filip Suba 2022-02-07 14:16:11 UTC

Verified with kmod-kvdo-8.1.1.287-12.el9

Comment 12 errata-xmlrpc 2022-05-17 15:49:47 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 (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