From: Bradley Morgan <bradley.morgan@linux.dev>
To: Christian Brauner <brauner@kernel.org>,
Serge Hallyn <serge@hallyn.com>, Paul Moore <paul@paul-moore.com>,
Josef Bacik <josef@toxicpanda.com>
Cc: James Morris <jmorris@namei.org>,
David Howells <dhowells@redhat.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
"Andrew G. Morgan" <morgan@kernel.org>,
Serge Hallyn <sergeh@kernel.org>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, keyrings@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v11 0/3] capabilities: close the ways around the CAP_SETFCAP rule for uid 0
Date: Fri, 20 Nov 2026 16:51:05 +0000 [thread overview]
Message-ID: <167100D4-9E3B-4412-A554-E3D09B5BE9DA@linux.dev> (raw)
In-Reply-To: <20261120-zutun-ausgearbeitet-erregen-ebd3834404ea@brauner>
On 20 November 2026 10:11:34 GMT, Christian Brauner <brauner@kernel.org>
wrote:
>On Tue, 17 Nov 2026 19:54:23 +0000, Josef Bacik wrote:
>> v1:
>https://lore.kernel.org/all/20261006-b4-setfcap-userns-v1-0-f47e7ed66072@toxicpanda.com/
>> v2:
>https://lore.kernel.org/all/20261014-b4-setfcap-userns-v2-0-fac4d19281d7@toxicpanda.com/
>> v3:
>https://lore.kernel.org/all/20261021-b4-setfcap-userns-v3-0-97c7ed4e43e1@toxicpanda.com/
>> v4:
>https://lore.kernel.org/all/20261022-b4-setfcap-userns-v4-0-88aa0ffaa08f@toxicpanda.com/
>> v5:
>https://lore.kernel.org/all/20261023-b4-setfcap-userns-v5-0-0620223be951@toxicpanda.com/
>> v6:
>https://lore.kernel.org/all/20261026-b4-setfcap-userns-v6-0-25f10b7ca497@toxicpanda.com/
>> v7:
>https://lore.kernel.org/all/20261026-b4-setfcap-userns-v7-0-bf8a576f7259@toxicpanda.com/
>> v8:
>https://lore.kernel.org/all/20261027-b4-setfcap-userns-v8-0-2674adc63f3c@toxicpanda.com/
>> v9:
>https://lore.kernel.org/all/20261109-b4-setfcap-userns-v9-0-0d3f00976ce2@toxicpanda.com/
>> v10:
>https://lore.kernel.org/all/20261112-b4-setfcap-userns-v10-0-84f6f7faa903@toxicpanda.com/
>>
>> [...]
>
>Applied to the namespace-7.5.misc branch of the vfs/vfs.git tree.
>Patches in the namespace-7.5.misc branch should appear in linux-next soon.
>
>Please report any outstanding bugs that were missed during review in a
>new review to the original patch series allowing us to drop it.
>
>It's encouraged to provide Acked-bys and Reviewed-bys even though the
>patch has now been applied. If possible patch trailers will be updated.
>
>Note that commit hashes shown below are subject to change due to rebase,
>trailer updates or similar. If in doubt, please check the listed branch.
>
>tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
>branch: namespace-7.5.misc
>
>[1/3] userns: don't let setns() lend CAP_SETFCAP
> https://git.kernel.org/vfs/vfs/c/711bc24f1d8f
>[2/3] capabilities: don't let ptrace borrow CAP_SETFCAP
> https://git.kernel.org/vfs/vfs/c/c1e5f4d36d2a
>[3/3] selftests/namespaces: test the CAP_SETFCAP rule for user namespaces
> https://git.kernel.org/vfs/vfs/c/cbe977960cb3
Oops! Couldn't get to it. I had a look, looks ^Wsane^W
Reviewed-by: Bradley Morgan <bradley.morgan@linux.dev>
>
--- Thanks!
prev parent reply other threads:[~2026-11-20 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 19:54 [PATCH v11 0/3] capabilities: close the ways around the CAP_SETFCAP rule for uid 0 Josef Bacik
2026-11-17 19:54 ` [PATCH v11 1/3] userns: don't let setns() lend CAP_SETFCAP Josef Bacik
2026-11-17 20:06 ` sashiko-bot
2026-11-20 17:22 ` Serge E. Hallyn
2026-11-20 17:34 ` Serge E. Hallyn
2026-11-17 19:54 ` [PATCH v11 2/3] capabilities: don't let ptrace borrow CAP_SETFCAP Josef Bacik
2026-11-17 20:13 ` sashiko-bot
2026-11-20 17:31 ` Serge E. Hallyn
2026-11-17 19:54 ` [PATCH v11 3/3] selftests/namespaces: test the CAP_SETFCAP rule for user namespaces Josef Bacik
2026-11-17 20:01 ` sashiko-bot
2026-11-20 10:11 ` [PATCH v11 0/3] capabilities: close the ways around the CAP_SETFCAP rule for uid 0 Christian Brauner
2026-11-20 16:51 ` Bradley Morgan [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=167100D4-9E3B-4412-A554-E3D09B5BE9DA@linux.dev \
--to=bradley.morgan@linux.dev \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=josef@toxicpanda.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=sergeh@kernel.org \
--cc=shuah@kernel.org \
/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.