From: Willy Tarreau <w@1wt.eu>
To: Marcelo Tosatti <marcelo@kvack.org>
Cc: Grant Coady <gcoady.lk@gmail.com>,
linux-kernel@vger.kernel.org, Al Viro <viro@ftp.linux.org.uk>
Subject: Re: Linux 2.4.33-rc1
Date: Tue, 20 Jun 2006 01:00:07 +0200 [thread overview]
Message-ID: <20060619230007.GA6471@1wt.eu> (raw)
In-Reply-To: <20060619220405.GA16251@dmt>
On Mon, Jun 19, 2006 at 07:04:05PM -0300, Marcelo Tosatti wrote:
> Think this is the right thing to do, except that it must be guaranteed
> that the inode struct won't be freed in the meantime, need to grab a
> reference to it.
OK, I believe it will be right this time. I took inspiration from your
precedent patch to sys_unlink().
diff --git a/fs/namei.c b/fs/namei.c
index 42cce98..374b767 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -1478,12 +1478,16 @@ exit:
int vfs_unlink(struct inode *dir, struct dentry *dentry)
{
int error;
+ struct inode *inode;
error = may_delete(dir, dentry, 0);
if (error)
return error;
- double_down(&dir->i_zombie, &dentry->d_inode->i_zombie);
+ inode = dentry->d_inode;
+ atomic_inc(&inode->i_count);
+ double_down(&dir->i_zombie, &inode->i_zombie);
+
error = -EPERM;
if (dir->i_op && dir->i_op->unlink) {
DQUOT_INIT(dir);
@@ -1495,7 +1499,9 @@ int vfs_unlink(struct inode *dir, struct
unlock_kernel();
}
}
- double_up(&dir->i_zombie, &dentry->d_inode->i_zombie);
+ double_up(&dir->i_zombie, &inode->i_zombie);
+ iput(inode);
+
if (!error) {
d_delete(dentry);
inode_dir_notify(dir, DN_DELETE);
BTW, I might be wrong because my knowledge in this area is rather poor, but
I now believe that your previously proposed fix below indeed is not needed
at all :
> diff --git a/fs/namei.c b/fs/namei.c
> index 42cce98..69da199 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -1509,6 +1511,7 @@ asmlinkage long sys_unlink(const char *
> char * name;
> struct dentry *dentry;
> struct nameidata nd;
> + struct inode *inode = NULL;
>
> name = getname(pathname);
> if(IS_ERR(name))
> @@ -1527,11 +1530,16 @@ asmlinkage long sys_unlink(const char *
> /* Why not before? Because we want correct error value */
> if (nd.last.name[nd.last.len])
> goto slashes;
---- from here ----
> + inode = dentry->d_inode;
> + if (inode)
> + atomic_inc(&inode->i_count);
> error = vfs_unlink(nd.dentry->d_inode, dentry);
> exit2:
> dput(dentry);
> }
> up(&nd.dentry->d_inode->i_sem);
> + if (inode)
> + iput(inode);
---- to here ----
I believe that nd.dentry->d_inode cannot vanish because it is protected by the
down(->i_sem) before and the up(->i_sem) after. Am I right or am I missing
something important ?
> exit1:
> path_release(&nd);
> exit:
Thanks,
Willy
next prev parent reply other threads:[~2006-06-19 23:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 18:14 Linux 2.4.33-rc1 Marcelo Tosatti
2006-06-16 22:21 ` Grant Coady
2006-06-16 22:38 ` Michal Piotrowski
2006-06-16 23:24 ` Grant Coady
2006-06-17 5:13 ` Willy Tarreau
2006-06-17 6:24 ` Grant Coady
2006-06-17 7:10 ` Willy Tarreau
2006-06-17 17:15 ` Need to format twice /dev/ramX with reiserfs to be able to mount it ? sebastien cabaniols
2006-06-17 18:14 ` Bernd Eckenfels
2006-06-17 18:37 ` sebastien cabaniols
2006-06-17 19:55 ` Linux 2.4.33-rc1 Marcelo Tosatti
2006-06-18 13:37 ` Marcelo Tosatti
2006-06-18 22:25 ` Grant Coady
2006-06-18 22:37 ` Willy Tarreau
2006-06-18 23:07 ` Grant Coady
2006-06-19 4:01 ` Willy Tarreau
2006-06-19 5:03 ` Grant Coady
2006-06-19 8:06 ` Willy Tarreau
2006-06-19 8:53 ` Grant Coady
2006-06-19 9:08 ` Willy Tarreau
2006-06-19 9:12 ` Grant Coady
2006-06-19 9:24 ` Willy Tarreau
2006-06-19 10:27 ` Grant Coady
2006-06-19 10:31 ` Willy Tarreau
2006-06-19 20:11 ` Grant Coady
2006-06-19 20:20 ` Willy Tarreau
2006-06-19 22:04 ` Marcelo Tosatti
2006-06-19 23:00 ` Willy Tarreau [this message]
2006-06-19 23:45 ` Marcelo Tosatti
2006-06-20 22:23 ` Willy Tarreau
2006-06-21 1:09 ` Grant Coady
2006-06-21 4:05 ` Willy Tarreau
2006-06-21 13:50 ` Marcelo Tosatti
2006-06-21 20:26 ` Willy Tarreau
2006-06-18 22:33 ` Grant Coady
2006-06-18 22:40 ` Willy Tarreau
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=20060619230007.GA6471@1wt.eu \
--to=w@1wt.eu \
--cc=gcoady.lk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.org \
--cc=viro@ftp.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.