Bug 1027601

Summary:	[RFE][rmmod] if module is in used, rmmod output the dependences
Product:	Red Hat Enterprise Linux 6	Reporter:	JianHong Yin <jiyin>
Component:	module-init-tools	Assignee:	David Shea <dshea>
Status:	CLOSED CANTFIX	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.6	Keywords:	FutureFeature
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1027600	Environment:
Last Closed:	2013-12-16 22:05:57 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:
Bug Depends On:	1027600
Bug Blocks:

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.