Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
On Azure RHEL8.8 ARM64 VMs, using below command to attempt to remove kernel module hv_utils yields no errors. hv_utils is then in fact not removed. dmesg seems to indicate a reload.
# modprobe -r hv_utils
# dmesg
...
[258680.893062] hv_utils: De-Registered HyperV Utility Driver
[258680.897060] hv_vmbus: unregistering driver hv_utils
[258680.942819] hv_utils: Registering HyperV Utility Driver
[258680.946193] hv_vmbus: registering driver hv_utils
[258680.949546] hv_utils: Shutdown IC version 3.2
[258682.902942] hv_utils: TimeSync IC version 4.0
[258684.292599] hv_utils: Heartbeat IC version 3.0
Version-Release number of selected component (if applicable):
4.18.0-445.el8.aarch64
# modinfo hv_utils
filename: /lib/modules/4.18.0-445.el8.aarch64/kernel/drivers/hv/hv_utils.ko.xz
license: GPL
description: Hyper-V Utilities
rhelversion: 8.8
srcversion: 3ACDFFE169B9A391A9356A5
alias: vmbus:e34bd134e4dec8419ae76b174977c192
alias: vmbus:292efa3523ea364296ae3a6ebacba440
alias: vmbus:e7f4a0a9455a964db8278a841e8c03e6
alias: vmbus:394f16571591784eab55382f3bd5422d
alias: vmbus:30e62795aed07b49adcee80ab0175caf
alias: vmbus:31600b0e13523449818b38d90ced39db
depends: hv_vmbus
intree: Y
name: hv_utils
vermagic: 4.18.0-445.el8.aarch64 SMP mod_unload modversions aarch64
sig_id: PKCS#7
signer: Red Hat Enterprise Linux kernel signing key
sig_key: 11:C7:7C:4A:BF:36:06:48:50:8E:04:9F:FD:D1:94:36:2F:9F:89:C3
sig_hashalgo: sha256
...
How reproducible:
100%
Steps to Reproduce:
1. # modprobe -r hv_utils or
2. # rmmod hv_utils
Actual results:
No error messages but module is not removed. dmesg indicates a reload.
Expected results:
Either this module will be successfully removed. Or an error message indicating it's in use should prompt.
Additional info:
No such issue on x86. An error message indicating module is in use will prompt.
Thanks for catching this bug!
Setting a low for now since there's no crash.
Comment 2RHEL Program Management
2023-09-22 14:24:31 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 3RHEL Program Management
2023-09-22 14:26:47 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.