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.

Bug 1140268

Summary: kpatch: support for re-enabling forced modules
Product: Red Hat Enterprise Linux 7 Reporter: Josh Poimboeuf <jpoimboe>
Component: kpatchAssignee: Seth Jennings <sjenning>
Status: CLOSED ERRATA QA Contact: Linqing Lu <lilu>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.0CC: jherrman, mmilgram, sjenning
Target Milestone: rcKeywords: ZStream
Target Release: 7.1   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kpatch-0.1.10-3.el7 Doc Type: Bug Fix
Doc Text:
It is now possible to re-enable patch modules which depend on the KPATCH_FORCE_UNSAFE script. This ensures that the "kpatch load" and "kpatch unload" commands always co-operate with the mentioned patch modules.
Story Points: ---
Clone Of:
: 1148852 (view as bug list) Environment:
Last Closed: 2015-03-05 13:40:28 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:
Bug Depends On:    
Bug Blocks: 1148852    

Description Josh Poimboeuf 2014-09-10 15:36:11 UTC
We need the ability to re-enable patch modules which rely on KPATCH_FORCE_UNSAFE, so that kpatch unload and load will always work with them.

This has already been fixed upstream with https://github.com/dynup/kpatch/pull/398.

Comment 4 Seth Jennings 2014-09-17 16:40:44 UTC
Linqing,

See previous comment for recreator patch.

Before:

# kpatch load kpatch-patch.ko 
loading core module: /root/kpatch/kpatch/../kmod/core/kpatch.ko
loading patch module: kpatch-patch.ko
# kpatch unload kpatch-patch.ko 
disabling patch module: kpatch_patch
unloading patch module: kpatch_patch
# kpatch load kpatch-patch.ko 
loading patch module: kpatch-patch.ko
insmod: ERROR: could not insert module kpatch-patch.ko: File exists
kpatch: failed to load module kpatch-patch.ko

After:

# kpatch load kpatch-patch.ko 
loading core module: /root/kpatch/kpatch/../kmod/core/kpatch.ko
loading patch module: kpatch-patch.ko
# kpatch unload kpatch-patch.ko 
disabling patch module: kpatch_patch
unloading patch module: kpatch_patch
# kpatch load kpatch-patch.ko 
module already loaded, re-enabling

Comment 5 Linqing Lu 2014-09-18 08:52:59 UTC
(In reply to Seth Jennings from comment #4)
> Linqing,
> 
> See previous comment for recreator patch.
> 

Thank you Seth!

Comment 10 errata-xmlrpc 2015-03-05 13:40:28 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://rhn.redhat.com/errata/RHBA-2015-0296.html