public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: PanBian <bianpan2016@163.com>
Cc: Jan Kara <jack@suse.cz>, Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH V2] namei: free new_dentry late
Date: Tue, 27 Nov 2018 11:05:36 +0100	[thread overview]
Message-ID: <20181127100536.GF16301@quack2.suse.cz> (raw)
In-Reply-To: <20181127095712.GA32100@bp>

On Tue 27-11-18 17:57:12, PanBian wrote:
> On Tue, Nov 27, 2018 at 10:25:51AM +0100, Jan Kara wrote:
> > On Sun 25-11-18 08:15:23, Pan Bian wrote:
> > > After calling dput(new_dentry), new_dentry is passed to fsnotify_move.
> > > This may result in a use-after-free bug. This patch moves the put
> > > operation late.
> > > 
> > > Fixes: da1ce0670c14("vfs: add cross-rename")
> > > Signed-off-by: Pan Bian <bianpan2016@163.com>
> > 
> > The code is actually fine AFAICT. One new_dentry reference is passed into
> > vfs_rename() and another one is acquired directly inside vfs_rename(). That
> > is the one dropped early but there's still the original reference passed in
> > protecting new_dentry from freeing. Am I missing something?
> 
> I am not quite sure about the actual execution logic. But I guess new_dentry 
> reference may be dropped outside vfs_rename in cocurrent executions.
> Otherwise, there is no need to acquire & drop new_dentry reference as it
> is always alive along vfs_rename.

I don't think that's the case. The dget() - dput() pair just looks
superfluous to me in vfs_rename(). Am I missing something Miklos?

								Honza

> > > diff --git a/fs/namei.c b/fs/namei.c
> > > index 0cab649..8b104d9 100644
> > > --- a/fs/namei.c
> > > +++ b/fs/namei.c
> > > @@ -4498,7 +4498,6 @@ int vfs_rename(struct inode *old_dir, struct dentry *old_dentry,
> > >  		unlock_two_nondirectories(source, target);
> > >  	else if (target)
> > >  		inode_unlock(target);
> > > -	dput(new_dentry);
> > >  	if (!error) {
> > >  		fsnotify_move(old_dir, new_dir, old_name.name, is_dir,
> > >  			      !(flags & RENAME_EXCHANGE) ? target : NULL, old_dentry);
> > > @@ -4507,6 +4506,7 @@ int vfs_rename(struct inode *old_dir, struct dentry *old_dentry,
> > >  				      new_is_dir, NULL, new_dentry);
> > >  		}
> > >  	}
> > > +	dput(new_dentry);
> > >  	release_dentry_name_snapshot(&old_name);
> > >  
> > >  	return error;
> > > -- 
> > > 2.7.4
> > > 
> > > 
> > -- 
> > Jan Kara <jack@suse.com>
> > SUSE Labs, CR
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2018-11-27 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25  0:15 [PATCH V2] namei: free new_dentry late Pan Bian
2018-11-27  9:25 ` Jan Kara
2018-11-27  9:57   ` PanBian
2018-11-27 10:05     ` Jan Kara [this message]
2018-11-27 10:33       ` Miklos Szeredi

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=20181127100536.GF16301@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=bianpan2016@163.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=viro@zeniv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox