Bug 1027601 - [RFE][rmmod] if module is in used, rmmod output the dependences
Summary: [RFE][rmmod] if module is in used, rmmod output the dependences
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: module-init-tools
Version: 6.6
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: David Shea
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 1027600
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-07 08:12 UTC by JianHong Yin
Modified: 2013-12-16 22:05 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1027600
Environment:
Last Closed: 2013-12-16 22:05:57 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description JianHong Yin 2013-11-07 08:12:27 UTC
+++ This bug was initially created as a clone of Bug #1027600 +++

Description of problem:
When we want rmmod the nfsd, the rmmod just tell me module "is in use".
  But not tell me who use it.
[root@dhcp12-144 ~]# rmmod nfsd
rmmod: ERROR: Module nfsd is in use   <<<--- NOT GOOD
[root@dhcp12-144 ~]# rmmod auth_rpcgss
rmmod: ERROR: Module auth_rpcgss is in use by: nfsd   <<<--- GOOD

And my buddy cost more than half an hours to find why can not rmmod,
  Finally we find it used by /proc/fs/nfsd.
Could rmmod output the dependences, if the dependences is not module name?

Version-Release number of selected component (if applicable):
all version in RHEL{5,6,7}

How reproducible:
100%

Steps to Reproduce:
1. rmmod nfsd
2.
3.

Actual results:
[root@dhcp12-144 ~]# rmmod nfsd
rmmod: ERROR: Module nfsd is in use 

Expected results:
[root@dhcp12-144 ~]# rmmod nfsd
rmmod: ERROR: Module nfsd is in use "by: /proc/fs/nfsd"
OR like follow (if difficult to get):
rmmod: ERROR: Module nfsd is in use "by: nil(maybe used by special filesystem)"

Additional info:

Comment 2 David Shea 2013-12-16 22:05:57 UTC
Closing for the same reason as bug 1027600: if module dependency list and the ref count are the only things that module-init-tools has to go on, so such a fix would have to begin in the kernel.


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