From: Jinjie Ruan <ruanjinjie@huawei.com>
To: "Serge E. Hallyn" <serge@hallyn.com>, Oleg Nesterov <oleg@redhat.com>
Cc: <kees@kernel.org>, <akpm@linux-foundation.org>,
<david@kernel.org>, <ljs@kernel.org>, <liam@infradead.org>,
<vbabka@kernel.org>, <rppt@kernel.org>, <surenb@google.com>,
<mhocko@suse.com>, <mingo@redhat.com>, <peterz@infradead.org>,
<juri.lelli@redhat.com>, <vincent.guittot@linaro.org>,
<dietmar.eggemann@arm.com>, <rostedt@goodmis.org>,
<bsegall@google.com>, <mgorman@suse.de>, <vschneid@redhat.com>,
<kprateek.nayak@amd.com>, <paul@paul-moore.com>,
<jmorris@namei.org>, <shuah@kernel.org>, <brauner@kernel.org>,
<alexjlzheng@tencent.com>, <jannh@google.com>,
<jaime.saguillo@gmail.com>, <elver@google.com>,
<blbllhy@gmail.com>, <bvanassche@acm.org>, <pjw@kernel.org>,
<broonie@kernel.org>, <debug@rivosinc.com>, <tglx@kernel.org>,
<aleksey.oladko@virtuozzo.com>, <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>,
<linux-security-module@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-kselftest@vger.kernel.org>, <morgan@kernel.org>
Subject: Re: [RFC PATCH v2 2/3] security: Add PR_CAPBSET_DROP_MASK for process-wide bounding-set drops
Date: Tue, 17 Nov 2026 15:08:18 +0800 [thread overview]
Message-ID: <ece02e4c-f87e-48ca-a653-cd02ca74eaba@huawei.com> (raw)
In-Reply-To: <avIVCf1ok6Xyfii0@hallyn.com>
在 2026/11/10 2:46, Serge E. Hallyn 写道:
> On Mon, Nov 09, 2026 at 07:00:51PM +0100, Oleg Nesterov wrote:
>> On 11/09, Serge E. Hallyn wrote:
>>>
>>> Hi Oleg,
>>>
>>> please see below. Do you have any issues with this use of sighand?
>>
>> Hi Serge,
>>
>> I already tried to look at this patch, but sorry, can't really comment.
>>
>> I'll try to take another look, but can't promise much, I don't understand
>> the problem space (I could never reallly understand capabilites in details).
>
> Thanks. I'm mainly wondering about the storing of this pending capability
> bounding mask in signal_struct, whether that might have any unexpected
Hi Serge,
rlimit is also placed inside the signal struct to implement
process-level restrictions.
I think the different lifetimes of cred and signal struct might be an
issue, but since drop only decreases and never increases, the result
seen by the user will only be stricter.
Link: https://lwn.net/Articles/103658/
Link:
https://github.com/torvalds/linux/commit/31180071ee5e6cc6ff4d036d655c556f582f74e4
Best regards,
Jinjie
> side effects.
next prev parent reply other threads:[~2026-11-17 7:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 13:01 [RFC PATCH v2 0/3] security: Add PR_CAPBSET_DROP_MASK Jinjie Ruan
2026-09-29 13:01 ` [RFC PATCH v2 1/3] capability: Move mk_kernel_cap() to header Jinjie Ruan
2026-09-29 13:06 ` sashiko-bot
2026-09-29 17:15 ` Bradley Morgan
2026-09-29 13:01 ` [RFC PATCH v2 2/3] security: Add PR_CAPBSET_DROP_MASK for process-wide bounding-set drops Jinjie Ruan
2026-09-29 13:19 ` sashiko-bot
2026-10-21 14:36 ` Serge E. Hallyn
2026-10-21 14:42 ` Andrew G. Morgan
2026-11-09 14:59 ` Serge E. Hallyn
2026-11-17 6:39 ` Jinjie Ruan
2026-11-09 14:58 ` Serge E. Hallyn
2026-11-09 18:00 ` Oleg Nesterov
2026-11-09 18:46 ` Serge E. Hallyn
2026-11-17 7:08 ` Jinjie Ruan [this message]
2026-09-29 13:02 ` [RFC PATCH v2 3/3] selftests: prctl: add process-wide bounding-set drop tests Jinjie Ruan
2026-09-29 13:11 ` sashiko-bot
2026-10-13 14:09 ` [RFC PATCH v2 0/3] security: Add PR_CAPBSET_DROP_MASK Serge E. Hallyn
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=ece02e4c-f87e-48ca-a653-cd02ca74eaba@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aleksey.oladko@virtuozzo.com \
--cc=alexjlzheng@tencent.com \
--cc=blbllhy@gmail.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=bsegall@google.com \
--cc=bvanassche@acm.org \
--cc=david@kernel.org \
--cc=debug@rivosinc.com \
--cc=dietmar.eggemann@arm.com \
--cc=elver@google.com \
--cc=jaime.saguillo@gmail.com \
--cc=jannh@google.com \
--cc=jmorris@namei.org \
--cc=juri.lelli@redhat.com \
--cc=kees@kernel.org \
--cc=kprateek.nayak@amd.com \
--cc=liam@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=morgan@kernel.org \
--cc=oleg@redhat.com \
--cc=paul@paul-moore.com \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=serge@hallyn.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=tglx@kernel.org \
--cc=vbabka@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@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