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 1511096 - modinfo output for kvdo module does not display version number
Summary: modinfo output for kvdo module does not display version number
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kmod-kvdo
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: corwin
QA Contact: Jakub Krysl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-08 16:38 UTC by Bryan Gurney
Modified: 2021-09-03 12:09 UTC (History)
3 users (show)

Fixed In Version: 6.1.0.51
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 16:25:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0900 0 None None None 2018-04-10 16:26:06 UTC

Description Bryan Gurney 2017-11-08 16:38:55 UTC 
Description of problem:
On a system where the "kmod-kvdo" package is installed, and the kvdo module has been added to the kernel via "modprobe" (e.g.: via a "vdo create" or "vdo start" command), running the "modinfo kvdo" program does not display the version of the currently running kvdo module.

This leads to confusion in situations where the kmod-kvdo package is being upgraded.  One example is in BZ 1510176, "yum remove kmod-kvdo does not unload kernel module".

Version-Release number of selected component (if applicable):
kmod-kvdo-6.1.0.34-7

How reproducible:
100%

Steps to Reproduce:
1. Install the "kmod-kvdo" and "vdo" packages (or select a base installation option).
2. Run "sudo vdo create" to create a VDO volume on a spare storage device.  (Alternatively, run "sudo modprobe kvdo"
3. Run "modinfo kvdo".

Actual results:
[root@rhel75test-20171023 ~]# modinfo kvdo
filename:       /lib/modules/3.10.0-768.el7.x86_64/weak-updates/kmod-kvdo/vdo/kvdo.ko
version:        
license:        GPL
author:         Red Hat, Inc.
description:    device-mapper target for transparent deduplication
rhelversion:    7.5
depends:        uds,dm-mod
vermagic:       3.10.0-766.el7.x86_64 SMP mod_unload modversions 


Expected results:
The "version" field displays a version number that matches with the kmod-kvdo package that was installed at the time of executing "modprobe kvdo".

Additional info:
Comment 2 Corey Marthaler 2017-11-10 20:33:55 UTC 
I assume this will fix the 'vdo status' version as well?

[root@mckinley-04 ~]# vdo status | more
VDO status:
  Date: '2017-11-10 14:32:28-06:00'
  Node: mckinley-04.lab.msp.redhat.com
Kernel module:
  Loaded: true
  Name: kvdo
  Version information:
    kvdo version: null

[...]
Comment 3 Bryan Gurney 2017-11-10 20:59:34 UTC 
(In reply to Corey Marthaler from comment #2)
> I assume this will fix the 'vdo status' version as well?
> 
> [root@mckinley-04 ~]# vdo status | more
> VDO status:
>   Date: '2017-11-10 14:32:28-06:00'
>   Node: mckinley-04.lab.msp.redhat.com
> Kernel module:
>   Loaded: true
>   Name: kvdo
>   Version information:
>     kvdo version: null
> 
> [...]

Yes; the version string from "modinfo kvdo" should print right after "kvdo version".
Comment 5 Jakub Krysl 2017-11-21 11:31:54 UTC 
kmod-kvdo 6.1.0.55-9.el7

# modinfo kvdo                 
filename:       /lib/modules/3.10.0-768.el7.x86_64/weak-updates/kmod-kvdo/vdo/kvdo.ko
version:        6.1.0.55
license:        GPL
author:         Red Hat, Inc.
description:    device-mapper target for transparent deduplication
rhelversion:    7.5
srcversion:     3250F953B508111FE3E0FB9
depends:        uds,dm-mod
vermagic:       3.10.0-783.el7.x86_64 SMP mod_unload modversions
Comment 8 errata-xmlrpc 2018-04-10 16:25:27 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, 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/RHEA-2018:0900
Note You need to log in before you can comment on or make changes to this bug.