Linux network filesystem support library
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Baokun Li <libaokun1@huawei.com>,
	netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	linux-erofs@lists.ozlabs.org, David Howells <dhowells@redhat.com>,
	Jeff Layton <jlayton@kernel.org>
Cc: stable@kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Christian Brauner <brauner@kernel.org>,
	Gao Xiang <hsiangkao@linux.alibaba.com>,
	Hou Tao <houtao1@huawei.com>,
	Jingbo Xu <jefflexu@linux.alibaba.com>,
	Yang Erkun <yangerkun@huawei.com>, Yu Kuai <yukuai3@huawei.com>,
	Zizhi Wo <wozizhi@huawei.com>
Subject: Re: [PATCH] cachefiles: fix dentry leak in cachefiles_open_file()
Date: Mon, 26 Aug 2024 15:55:44 +0200	[thread overview]
Message-ID: <467d9b9b-34b4-4a94-95c1-1d41f0a91e05@web.de> (raw)
In-Reply-To: <20240826040018.2990763-1-libaokun@huaweicloud.com>

…
> Add the missing dput() to cachefiles_open_file() for a quick fix.

I suggest to use a goto chain accordingly.


…
> +++ b/fs/cachefiles/namei.c
> @@ -554,6 +554,7 @@ static bool cachefiles_open_file(struct cachefiles_object *object,
>  	if (!cachefiles_mark_inode_in_use(object, d_inode(dentry))) {
>  		pr_notice("cachefiles: Inode already in use: %pd (B=%lx)\n",
>  			  dentry, d_inode(dentry)->i_ino);
> +		dput(dentry);
>  		return false;

Please replace two statements by the statement “goto put_dentry;”.


…
> error:
> 	cachefiles_do_unmark_inode_in_use(object, d_inode(dentry));
+put_dentry:
> 	dput(dentry);
> 	return false;
> }

Regards,
Markus

  reply	other threads:[~2024-08-26 13:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26  4:00 [PATCH] cachefiles: fix dentry leak in cachefiles_open_file() libaokun
2024-08-26 13:55 ` Markus Elfring [this message]
2024-08-27  3:47   ` Baokun Li
2024-08-27  8:34     ` Markus Elfring
2024-08-28 13:01     ` [PATCH] " David Howells
2024-08-28 14:05       ` Baokun Li
2024-08-28 16:14         ` David Howells
2024-08-29  1:43           ` Baokun Li

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=467d9b9b-34b4-4a94-95c1-1d41f0a91e05@web.de \
    --to=markus.elfring@web.de \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=houtao1@huawei.com \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=jefflexu@linux.alibaba.com \
    --cc=jlayton@kernel.org \
    --cc=libaokun1@huawei.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfs@lists.linux.dev \
    --cc=stable@kernel.org \
    --cc=wozizhi@huawei.com \
    --cc=yangerkun@huawei.com \
    --cc=yukuai3@huawei.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