From: patchwork-bot+netdevbpf@kernel.org
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
jack@suse.cz, kees@kernel.org, linux-mm@kvack.org,
bpf@vger.kernel.org, farid.m.zakaria@gmail.com, corbet@lwn.net,
jannh@google.com, mail@johnericson.me, stable@vger.kernel.org
Subject: Re: [PATCH] binfmt_misc: don't leak the user namespace when the mount fails
Date: Sun, 09 Aug 2026 22:37:44 +0000 [thread overview]
Message-ID: <178631506414.3049071.14867849911905814452.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260728-work-binfmt_misc-usernsleak-v1-1-dbd8d5e626e7@kernel.org>
Hello:
This patch was applied to bpf/bpf.git (master)
by Christian Brauner <brauner@kernel.org>:
On Tue, 28 Jul 2026 15:48:10 +0200 you wrote:
> bm_get_tree() takes a reference to the user namespace and hands it to
> get_tree_keyed() as the sget key. sget_fc() moves that reference into
> sb->s_fs_info and clears fc->s_fs_info, so from that point on the
> superblock owns it and bm_free() doesn't see it anymore.
>
> The superblock drops it in ->put_super(). But generic_shutdown_super()
> only calls ->put_super() from inside the if (sb->s_root) branch, so
> nothing releases it when bm_fill_super() fails:
>
> [...]
Here is the summary with links:
- binfmt_misc: don't leak the user namespace when the mount fails
https://git.kernel.org/bpf/bpf/c/b8206f516fe7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-09 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 13:48 [PATCH] binfmt_misc: don't leak the user namespace when the mount fails Christian Brauner
2026-08-09 22:37 ` patchwork-bot+netdevbpf [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=178631506414.3049071.14867849911905814452.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=farid.m.zakaria@gmail.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mail@johnericson.me \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.