Linux NFS development
 help / color / mirror / Atom feed
From: Olaf Kirch <okir@suse.de>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] SGI 882960: Busy inodes after unmount, oops
Date: Thu, 5 Feb 2004 17:15:15 +0100	[thread overview]
Message-ID: <20040205161515.GA21344@suse.de> (raw)
In-Reply-To: <4021751C.B888A15C@melbourne.sgi.com>

Hi Greg,

On Thu, Feb 05, 2004 at 09:41:32AM +1100, Greg Banks wrote:
> BTW (not directly related to this bug) I found by experiment that I
> could umount an NFS mount when there were open file descriptors for
> unlinked files in the mount, and even keep writing.  All the NFS
> and RPC structures stay alive until the last file descriptor closes,
> thanks to the magic of refcounts.  All this despite the vfsmount
> reference taken in struct file, which I thought was supposed to
> prevent umount.

Then something else must be wrong big time.

> >  -      __rpc_execute notices the task is dead (no tk_action),
> >         leaves the loop and invokes task->tk_exit == nfs_async_unlink_done
> 
> No.  In a crash dump taken after the umount has completed, the dir dentry has
> 1 leaked d_count for every async unlink present at umount, even though the
> async unlink tasks have been cleaned up.  This indicates that task->tk_exit
> is not being called but task->tk_release is, so the dput is not happening.

But then prune_dcache shouldn't touch these dentries at all, because their
refcount is still 1. They would be leaked, but there would be no crash.

> It's not entirely clear to me how __rpc_execute can do that, but the evidence
> is that it does so.

Very strange... maybe we have a refcounting problem elsewhere, and the
refcount was 2 before calling tk_exit? But somehow I doubt this... I
think we'd see far more massive problems in this case.

Would you share your test case?

Olaf
-- 
Olaf Kirch     |  Stop wasting entropy - start using predictable
okir@suse.de   |  tempfile names today!
---------------+ 


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-02-05 16:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04  7:12 [PATCH] SGI 882960: Busy inodes after unmount, oops Greg Banks
2004-02-04 10:42 ` Olaf Kirch
2004-02-04 22:59   ` Greg Banks
2004-02-04 12:09 ` Olaf Kirch
2004-02-04 22:41   ` Greg Banks
2004-02-05 16:15     ` Olaf Kirch [this message]
2004-02-05 22:23       ` Greg Banks
2004-02-06  5:50         ` Greg Banks
2004-02-13 16:26           ` canon
2004-02-04 14:24 ` raven
2004-02-04 22:56   ` Greg Banks
2004-02-05 12:40 ` James Pearson
2004-02-09  7:46   ` Greg Banks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040205161515.GA21344@suse.de \
    --to=okir@suse.de \
    --cc=gnb@melbourne.sgi.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox