xfs
[Top] [All Lists]

CLOSE 787669 - page_buf_locking could not be rmmod'ed

To: ananth@xxxxxxxxxxxxxxxxxxxx
Subject: CLOSE 787669 - page_buf_locking could not be rmmod'ed
From: pv@xxxxxxxxxxxxxxxxxxxxxx (lord@xxxxxxx)
Date: Wed, 28 Jun 2000 08:08:54 -0700 (PDT)
Cc: linux-xfs@xxxxxxxxxxx
Reply-to: sgi.bugs.xfs@xxxxxxxxxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
Webexec: bugs_update,pvincident
Webpv: 192.82.201.231
View Incident: 
http://co-op.engr.sgi.com/BugWorks/code/bwxquery.cgi?search=Search&wlong=1&view_type=Bug&wi=787669

*Status : closed                       Priority : 2                         
 Assigned Engineer : ananth            Submitter : mostek                   
 Opened Date : 04/11/00               *Closed Date : 06/28/00               
*Fixed By : lord                      *Fixed By Domain : sgi.com            
*Modified Date : 06/28/00             *Modified User : lord                 
*Modified User Domain : sgi.com       *Fix Description :
==========================
ADDITIONAL INFORMATION (CLOSE)
From: lord@xxxxxxx (BWX)
Date: Jun 28 2000 08:08:53AM
==========================

Closing PVs which were fixed in the XFS linux port a long time
ago.
Description :
Got into a situation where the use count for the page_buf_locking
module was greater than zero, even though the xfs module had been
unloaded, and therefore I am unable to unload the module.  A quick
look around, found this:

xfs_super.c:
  void
  linvfs_release_inode(struct inode *inode)
  {
        if (inode) {

.....


==========================
ADDITIONAL INFORMATION (ADD)
From: lord@xxxxxxx (BugWorks)
Date: Apr 11 2000 08:00:57AM
==========================

I think this is actually a side effect of BUG 787427 where there
are page_bufs left around after unmount. This is the reason for
the EBUSY - and any form of looping is not going to fix it, we
need to get the buffers out of memory duing unmount.

<Prev in Thread] Current Thread [Next in Thread>
  • CLOSE 787669 - page_buf_locking could not be rmmod'ed, lord@xxxxxxx <=