public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: Pan Bian <bianpan2016@163.com>, Chris Mason <clm@fb.com>,
	David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [V2] btrfs: drop inode reference count on error path
Date: Thu, 18 Apr 2019 17:09:44 +0300	[thread overview]
Message-ID: <bf1a23fa-d9e3-3fd4-8cf5-2ed53225fe11@suse.com> (raw)
In-Reply-To: <20190418140749.h57y5kqz4s47sbuo@macbook-pro-91.dhcp.thefacebook.com>



On 18.04.19 г. 17:07 ч., Josef Bacik wrote:
> On Thu, Apr 18, 2019 at 03:50:00PM +0300, Nikolay Borisov wrote:
>>
>>
>> On 18.04.19 г. 14:06 ч., Pan Bian wrote:
>>> The reference count of inode is incremented by ihold. It should be
>>> dropped if not used. However, the reference count is not dropped if
>>> error occurs during updating the inode or deleting orphan items. This
>>> patch fixes the bug.
>>>
>>> Signed-off-by: Pan Bian <bianpan2016@163.com>
>>> ---
>>> V2: move ihold just before device_initialize to make code clearer
>>> ---
>>>  fs/btrfs/inode.c | 54 +++++++++++++++++++++++++-----------------------------
>>>  1 file changed, 25 insertions(+), 29 deletions(-)
>>>
>>> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
>>> index 82fdda8..d6630df 100644
>>> --- a/fs/btrfs/inode.c
>>> +++ b/fs/btrfs/inode.c
>>> @@ -6579,7 +6579,7 @@ static int btrfs_link(struct dentry *old_dentry, struct inode *dir,
>>>  	struct btrfs_fs_info *fs_info = btrfs_sb(inode->i_sb);
>>>  	u64 index;
>>>  	int err;
>>> -	int drop_inode = 0;
>>> +	int log_mode;
>>>  
>>>  	/* do not allow sys_link's with other subvols of the same device */
>>>  	if (root->root_key.objectid != BTRFS_I(inode)->root->root_key.objectid)
>>> @@ -6616,41 +6616,37 @@ static int btrfs_link(struct dentry *old_dentry, struct inode *dir,
>>>  	err = btrfs_add_nondir(trans, BTRFS_I(dir), dentry, BTRFS_I(inode),
>>>  			1, index);
>>>  
>>> -	if (err) {
>>> -		drop_inode = 1;
>>> -	} else {
>>> -		struct dentry *parent = dentry->d_parent;
>>> -		int ret;
>>> +	if (err)
>>> +		goto err_link;
>>>  
>>> -		err = btrfs_update_inode(trans, root, inode);
>>> +	err = btrfs_update_inode(trans, root, inode);
>>> +	if (err)
>>> +		goto err_link;
>>> +	if (inode->i_nlink == 1) {
>>> +		/*
>>> +		 * If new hard link count is 1, it's a file created
>>> +		 * with open(2) O_TMPFILE flag.
>>> +		 */
>>> +		err = btrfs_orphan_del(trans, BTRFS_I(inode));
>>>  		if (err)
>>> -			goto fail;
>>> -		if (inode->i_nlink == 1) {
>>> -			/*
>>> -			 * If new hard link count is 1, it's a file created
>>> -			 * with open(2) O_TMPFILE flag.
>>> -			 */
>>> -			err = btrfs_orphan_del(trans, BTRFS_I(inode));
>>> -			if (err)
>>> -				goto fail;
>>> -		}
>>> -		BTRFS_I(inode)->last_link_trans = trans->transid;
>>> -		d_instantiate(dentry, inode);
>>> -		ret = btrfs_log_new_name(trans, BTRFS_I(inode), NULL, parent,
>>> -					 true, NULL);
>>> -		if (ret == BTRFS_NEED_TRANS_COMMIT) {
>>> -			err = btrfs_commit_transaction(trans);
>>> -			trans = NULL;
>>> -		}
>>> +			goto err_link;
>>> +	}
>>> +	BTRFS_I(inode)->last_link_trans = trans->transid;
>>> +	ihold(inode);
> 
> Where is the iput for this ihold?

This ihold is sort of "given" to the d_instantiate. I.e the iput happens
when the respective dentry is unhashed/removed.

> 
> Josef
> 

  reply	other threads:[~2019-04-18 14:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 11:06 [V2] btrfs: drop inode reference count on error path Pan Bian
2019-04-18 12:50 ` Nikolay Borisov
2019-04-18 14:07   ` Josef Bacik
2019-04-18 14:09     ` Nikolay Borisov [this message]
2019-04-18 14:11       ` Josef Bacik
2019-05-02 14:32 ` David Sterba

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=bf1a23fa-d9e3-3fd4-8cf5-2ed53225fe11@suse.com \
    --to=nborisov@suse.com \
    --cc=bianpan2016@163.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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