From: Miklos Szeredi <miklos@szeredi.hu>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
overlayfs <linux-unionfs@vger.kernel.org>,
"Amir Goldstein" <amir73il@gmail.com>,
"Vivek Goyal" <vgoyal@redhat.com>,
stable <stable@vger.kernel.org>,
syzbot <syzkaller@googlegroups.com>,
"Mickaël Salaün" <mic@linux.microsoft.com>
Subject: Re: [PATCH v1] ovl: Fix leaked dentry
Date: Thu, 8 Apr 2021 11:58:10 +0200 [thread overview]
Message-ID: <CAJfpegu=8L7Fd_qYK0cJRQ18NqyVeSvTp-vcC4KmqZEcw28naw@mail.gmail.com> (raw)
In-Reply-To: <20210329164907.2133175-1-mic@digikod.net>
On Mon, Mar 29, 2021 at 6:48 PM Mickaël Salaün <mic@digikod.net> wrote:
>
> From: Mickaël Salaün <mic@linux.microsoft.com>
>
> Since commit 6815f479ca90 ("ovl: use only uppermetacopy state in
> ovl_lookup()"), overlayfs doesn't put temporary dentry when there is a
> metacopy error, which leads to dentry leaks when shutting down the
> related superblock:
>
> overlayfs: refusing to follow metacopy origin for (/file0)
> ...
> BUG: Dentry (____ptrval____){i=3f33,n=file3} still in use (1) [unmount of overlay overlay]
> ...
> WARNING: CPU: 1 PID: 432 at umount_check.cold+0x107/0x14d
> CPU: 1 PID: 432 Comm: unmount-overlay Not tainted 5.12.0-rc5 #1
> ...
> RIP: 0010:umount_check.cold+0x107/0x14d
> ...
> Call Trace:
> d_walk+0x28c/0x950
> ? dentry_lru_isolate+0x2b0/0x2b0
> ? __kasan_slab_free+0x12/0x20
> do_one_tree+0x33/0x60
> shrink_dcache_for_umount+0x78/0x1d0
> generic_shutdown_super+0x70/0x440
> kill_anon_super+0x3e/0x70
> deactivate_locked_super+0xc4/0x160
> deactivate_super+0xfa/0x140
> cleanup_mnt+0x22e/0x370
> __cleanup_mnt+0x1a/0x30
> task_work_run+0x139/0x210
> do_exit+0xb0c/0x2820
> ? __kasan_check_read+0x1d/0x30
> ? find_held_lock+0x35/0x160
> ? lock_release+0x1b6/0x660
> ? mm_update_next_owner+0xa20/0xa20
> ? reacquire_held_locks+0x3f0/0x3f0
> ? __sanitizer_cov_trace_const_cmp4+0x22/0x30
> do_group_exit+0x135/0x380
> __do_sys_exit_group.isra.0+0x20/0x20
> __x64_sys_exit_group+0x3c/0x50
> do_syscall_64+0x45/0x70
> entry_SYSCALL_64_after_hwframe+0x44/0xae
> ...
> VFS: Busy inodes after unmount of overlay. Self-destruct in 5 seconds. Have a nice day...
>
> This fix has been tested with a syzkaller reproducer.
>
> Cc: Amir Goldstein <amir73il@gmail.com>
> Cc: Miklos Szeredi <miklos@szeredi.hu>
> Cc: Vivek Goyal <vgoyal@redhat.com>
> Cc: <stable@vger.kernel.org> # v5.7+
> Reported-by: syzbot <syzkaller@googlegroups.com>
> Fixes: 6815f479ca90 ("ovl: use only uppermetacopy state in ovl_lookup()")
> Signed-off-by: Mickaël Salaün <mic@linux.microsoft.com>
> Link: https://lore.kernel.org/r/20210329164907.2133175-1-mic@digikod.net
Thanks, applied.
Miklos
prev parent reply other threads:[~2021-04-08 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 16:49 [PATCH v1] ovl: Fix leaked dentry Mickaël Salaün
2021-03-30 9:44 ` Mickaël Salaün
2021-04-01 15:58 ` Vivek Goyal
2021-04-01 16:50 ` Vivek Goyal
2021-04-08 9:58 ` Miklos Szeredi [this message]
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='CAJfpegu=8L7Fd_qYK0cJRQ18NqyVeSvTp-vcC4KmqZEcw28naw@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mic@digikod.net \
--cc=mic@linux.microsoft.com \
--cc=stable@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=vgoyal@redhat.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;
as well as URLs for NNTP newsgroup(s).