Linux NFS development
 help / color / mirror / Atom feed
From: Frank Cusack <fcusack@fcusack.com>
To: Matt C <wago@phlinux.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Olaf Hering <olh@suse.de>, "H. Peter Anvin" <hpa@zytor.com>,
	Arun Sharma <arun.sharma@intel.com>,
	autofs@linux.kernel.org, nfs@lists.sourceforge.net,
	Ian Kent <raven@themaw.net>
Subject: Re: Re: [autofs] VFS: Busy inodes after unmount on 2 way SMP
Date: Sun, 28 Sep 2003 20:27:58 -0700	[thread overview]
Message-ID: <20030928202757.A21288@google.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0309251614290.22478-100000@fubar.phlinux.com>; from wago@phlinux.com on Thu, Sep 25, 2003 at 04:17:54PM -0700

Does this patch help?

--- linux-2.4.22/fs/namei.c	2003-08-25 04:44:43.000000000 -0700
+++ linux-2.4.22-gg4/fs/namei.c	2003-09-26 00:03:16.000000000 -0700
@@ -893,6 +893,8 @@ static inline int check_sticky(struct in
  *  7. If we were asked to remove a directory and victim isn't one - ENOTDIR.
  *  8. If we were asked to remove a non-directory and victim isn't one - EISDIR.
  *  9. We can't remove a root or mountpoint.
+ * 10. We don't allow removal of NFS sillyrenamed files; it's handled by
+ *     nfs_async_unlink().
  */
 static inline int may_delete(struct inode *dir,struct dentry *victim, int isdir)
 {
@@ -916,6 +918,8 @@ static inline int may_delete(struct inod
 		return -EISDIR;
 	if (IS_DEADDIR(dir))
 		return -ENOENT;
+	if (victim->d_flags & DCACHE_NFSFS_RENAMED)
+		return -EBUSY;
 	return 0;
 }
 
@@ -1484,13 +1488,14 @@ int vfs_unlink(struct inode *dir, struct
 				lock_kernel();
 				error = dir->i_op->unlink(dir, dentry);
 				unlock_kernel();
-				if (!error)
+				if (!error &&
+				    !(dentry->d_flags & DCACHE_NFSFS_RENAMED))
 					d_delete(dentry);
 			}
 		}
 	}
 	up(&dir->i_zombie);
-	if (!error)
+	if (!error && !(dentry->d_flags & DCACHE_NFSFS_RENAMED))
 		inode_dir_notify(dir, DN_DELETE);
 	return error;
 }


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      parent reply	other threads:[~2003-09-29  5:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0309171251290.25153-100000@wombat.indigo.net.au>
     [not found] ` <3F689E40.6090802@intel.com>
     [not found]   ` <3F68C6EB.2080706@zytor.com>
     [not found]     ` <20030917210023.GA15099@suse.de>
2003-09-18  5:52       ` Re: [autofs] VFS: Busy inodes after unmount on 2 way SMP Trond Myklebust
2003-09-18  8:26         ` Olaf Kirch
2003-09-25 23:17         ` Matt C
2003-09-26  0:24           ` Trond Myklebust
     [not found]             ` <200309261831.h8QIVNVw026806@buggy.badula.org>
2003-09-26 22:29               ` Trond Myklebust
2003-09-27 16:55                 ` Olaf Kirch
2003-09-28 23:16                   ` Steve Fosdick
2003-09-29 12:07                 ` Ion Badulescu
2003-09-29 17:22                   ` Trond Myklebust
2003-09-30 12:50                     ` Olaf Kirch
2003-09-30 13:31                       ` Trond Myklebust
2003-09-29  3:27           ` Frank Cusack [this message]

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=20030928202757.A21288@google.com \
    --to=fcusack@fcusack.com \
    --cc=arun.sharma@intel.com \
    --cc=autofs@linux.kernel.org \
    --cc=hpa@zytor.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=olh@suse.de \
    --cc=raven@themaw.net \
    --cc=trond.myklebust@fys.uio.no \
    --cc=wago@phlinux.com \
    /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