From: Christian Brauner <brauner@kernel.org>
To: Deepanshu Kartikey <kartikey406@gmail.com>
Cc: viro@zeniv.linux.org.uk, jack@suse.cz, mszeredi@redhat.com,
raven@themaw.net, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+e4470cc28308f2081ec8@syzkaller.appspotmail.com
Subject: Re: [PATCH] fs/namespace: fix double hlist_del_init of mnt_mp_list in get_detached_copy()
Date: Sat, 21 Mar 2026 09:22:01 +0100 [thread overview]
Message-ID: <20260321-preschen-karitativ-508756cc870f@brauner> (raw)
In-Reply-To: <20260321062412.1120693-1-kartikey406@gmail.com>
On Sat, Mar 21, 2026 at 11:54:12AM +0530, Deepanshu Kartikey wrote:
> get_detached_copy() builds a new anonymous mount namespace for
> open_tree(OPEN_TREE_CLONE) by iterating all mounts in the cloned tree
> and calling mnt_add_to_ns() for each. However, child mounts in the
> cloned tree have their mnt_mp_list linked into the original mountpoint's
> m_list via mnt_set_mountpoint(). mnt_add_to_ns() only updates the
> namespace RB tree and never removes mnt_mp_list from that list.
>
> When both the original and new anonymous namespaces are torn down on
> process exit, put_mnt_ns() -> umount_tree() -> __umount_mnt() calls
> hlist_del_init() on mnt_mp_list for each mount. Since the same mount
> belongs to two namespaces, hlist_del_init() is called twice on the same
> node, corrupting the list and causing a general protection fault.
>
> Fix this by calling hlist_del_init() on mnt_mp_list and clearing mnt_mp
> for each mount inside the loop in get_detached_copy(). This detaches
> them from the original mountpoint's m_list. Clearing mnt_mp also
> prevents __umount_mnt() from passing a stale pointer to
> maybe_free_mountpoint() during teardown.
>
> Reported-by: syzbot+e4470cc28308f2081ec8@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=e4470cc28308f2081ec8
> Tested-by: syzbot+e4470cc28308f2081ec8@syzkaller.appspotmail.com
> Fixes: 2eea9ce4310d ("mounts: keep list of mounts in an rbtree")
> Signed-off-by: Deepanshu kartikey <Kartikey406@gmail.com>
> ---
Both the analysis and the fix are unfortunately very wrong.
The original cuplrit is how we create partial mount namespace copies.
I have a fix for that ready to go later.
prev parent reply other threads:[~2026-03-21 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 6:24 [PATCH] fs/namespace: fix double hlist_del_init of mnt_mp_list in get_detached_copy() Deepanshu Kartikey
2026-03-21 8:22 ` Christian Brauner [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=20260321-preschen-karitativ-508756cc870f@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=kartikey406@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=raven@themaw.net \
--cc=syzbot+e4470cc28308f2081ec8@syzkaller.appspotmail.com \
--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