From: David Howells <dhowells@redhat.com>
To: libaokun@huaweicloud.com
Cc: dhowells@redhat.com, netfs@lists.linux.dev, jlayton@kernel.org,
brauner@kernel.org, linux-fsdevel@vger.kernel.org,
hsiangkao@linux.alibaba.com, jefflexu@linux.alibaba.com,
linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
yangerkun@huawei.com, houtao1@huawei.com, yukuai3@huawei.com,
wozizhi@huawei.com, Baokun Li <libaokun1@huawei.com>,
stable@kernel.org
Subject: Re: [PATCH v2] cachefiles: fix dentry leak in cachefiles_open_file()
Date: Mon, 16 Sep 2024 14:05:09 +0100 [thread overview]
Message-ID: <1899865.1726491909@warthog.procyon.org.uk> (raw)
In-Reply-To: <20240829083409.3788142-1-libaokun@huaweicloud.com>
libaokun@huaweicloud.com wrote:
> From: Baokun Li <libaokun1@huawei.com>
>
> A dentry leak may be caused when a lookup cookie and a cull are concurrent:
>
> P1 | P2
> -----------------------------------------------------------
> cachefiles_lookup_cookie
> cachefiles_look_up_object
> lookup_one_positive_unlocked
> // get dentry
> cachefiles_cull
> inode->i_flags |= S_KERNEL_FILE;
> cachefiles_open_file
> cachefiles_mark_inode_in_use
> __cachefiles_mark_inode_in_use
> can_use = false
> if (!(inode->i_flags & S_KERNEL_FILE))
> can_use = true
> return false
> return false
> // Returns an error but doesn't put dentry
>
> After that the following WARNING will be triggered when the backend folder
> is umounted:
>
> ==================================================================
> BUG: Dentry 000000008ad87947{i=7a,n=Dx_1_1.img} still in use (1) [unmount of ext4 sda]
> WARNING: CPU: 4 PID: 359261 at fs/dcache.c:1767 umount_check+0x5d/0x70
> CPU: 4 PID: 359261 Comm: umount Not tainted 6.6.0-dirty #25
> RIP: 0010:umount_check+0x5d/0x70
> Call Trace:
> <TASK>
> d_walk+0xda/0x2b0
> do_one_tree+0x20/0x40
> shrink_dcache_for_umount+0x2c/0x90
> generic_shutdown_super+0x20/0x160
> kill_block_super+0x1a/0x40
> ext4_kill_sb+0x22/0x40
> deactivate_locked_super+0x35/0x80
> cleanup_mnt+0x104/0x160
> ==================================================================
>
> Whether cachefiles_open_file() returns true or false, the reference count
> obtained by lookup_positive_unlocked() in cachefiles_look_up_object()
> should be released.
>
> Therefore release that reference count in cachefiles_look_up_object() to
> fix the above issue and simplify the code.
>
> Fixes: 1f08c925e7a3 ("cachefiles: Implement backing file wrangling")
> Cc: stable@kernel.org
> Signed-off-by: Baokun Li <libaokun1@huawei.com>
Acked-by: David Howells <dhowells@redhat.com>
next prev parent reply other threads:[~2024-09-16 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 8:34 [PATCH v2] cachefiles: fix dentry leak in cachefiles_open_file() libaokun
2024-09-16 13:05 ` David Howells [this message]
2024-09-17 9:03 ` Christian Brauner
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=1899865.1726491909@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=brauner@kernel.org \
--cc=houtao1@huawei.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=jefflexu@linux.alibaba.com \
--cc=jlayton@kernel.org \
--cc=libaokun1@huawei.com \
--cc=libaokun@huaweicloud.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