Bug 610224 - running 'rmmod wifi-driver-module' in fips mode hangs system
running 'rmmod wifi-driver-module' in fips mode hangs system
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
6.0
All Linux
medium Severity medium
: rc
: ---
Assigned To: John W. Linville
desktop-bugs@redhat.com
:
Depends On:
Blocks: 582655 608704
  Show dependency treegraph
 
Reported: 2010-07-01 15:24 EDT by Jiri Kastner
Modified: 2010-11-11 11:05 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-11 11:05:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
IMG00061-20100707-1446.jpg (910.23 KB, image/jpeg)
2010-07-07 14:58 EDT, John W. Linville
no flags Details
jwltest-ath9k-cleanup-init-error-path.patch (1.96 KB, patch)
2010-07-08 16:46 EDT, John W. Linville
no flags Details | Diff

  None (edit)
Description Jiri Kastner 2010-07-01 15:24:25 EDT
Description of problem:
in fips mode, every attempt to remove ath9k module hangs/freeze system

Version-Release number of selected component (if applicable):
kernel-2.6.32-37.el6.x86_64


How reproducible:
always

Steps to Reproduce:
1. enable fips mode
2. rmmod ath9k
3. system unusable
  
Actual results:
system hangs

Expected results:
removing of module will work as for other modules in fips mode

Additional info:
Comment 1 RHEL Product and Program Management 2010-07-01 15:43:11 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 2 Stanislaw Gruszka 2010-07-02 07:18:52 EDT
What is fips mode? How to enable it?
Comment 3 John W. Linville 2010-07-02 10:52:26 EDT
FWIW, this likely results from some failed clean-up after ieee80211_register_hw fails...
Comment 4 Jiri Kastner 2010-07-07 04:30:52 EDT
renamed, because i noticed this on iwlagn with john's test kernel
Comment 5 John W. Linville 2010-07-07 14:54:35 EDT
FWIW, I think this actually is ath9k-specific.  The similar behavior on iwlagn was actually caused by the 1st fix attempt in bug 608704.  After fixing that issue, I was still able to get this ath9k failure.  I'll attach a pic of the failure on my local machine.
Comment 6 John W. Linville 2010-07-07 14:58:06 EDT
Created attachment 430156 [details]
IMG00061-20100707-1446.jpg

Note that this is without the fix to allow FIPS mode to work (but with the fix that allows rmmod of iwlagn) -- with that in place I suspect this won't happen at all.
Comment 8 John W. Linville 2010-07-08 16:46:04 EDT
Created attachment 430471 [details]
jwltest-ath9k-cleanup-init-error-path.patch
Comment 9 Jiri Kastner 2010-07-11 05:22:08 EDT
verified with adapters, where i detected. rmmod iwlagn and ath9k works as expected
Comment 13 Aristeu Rozanski 2010-07-26 11:15:54 EDT
Patch(es) available on kernel-2.6.32-52.el6
Comment 16 Vladimir Benes 2010-08-24 04:51:08 EDT
Jiri,
Could you please retest so we can close this? Or you can alternatively write here hostname where we can retest.

thanks,
Vlad
Comment 17 Vladimir Benes 2010-08-26 08:54:41 EDT
tested on frankenstein-wifi-01.rhts.eng.bos.redhat.com, it has several types of wireless devices. Tested with all of them under fips enabled system.
rt61pci,rt73usb, ath5k, ath9k, rtl8180, rtl8187

looks good 
-> VERIFIED
Comment 18 releng-rhel@redhat.com 2010-11-11 11:05:50 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.