mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: 양시은 <didtldms2525@naver.com>
To: "Mickaël Salaün" <mic@digikod.net>,
	"Hungyu Lin" <dennylin0707@gmail.com>
Cc: hannes@cmpxchg.org, surenb@google.com, peterz@infradead.org,
	mingo@redhat.com, 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,
	cerasuolodomenico@gmail.com, linux-kernel@vger.kernel.org,
	sashiko-bot@kernel.org, "Günther Noack" <gnoack3000@gmail.com>,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH] sched/psi: Check CAP_SYS_RESOURCE in the initial user namespace
Date: Tue, 10 Nov 2026 09:49:16 +0900	[thread overview]
Message-ID: <e360517ba7fa8262912a5c01b224ad9@cweb016.nm> (raw)
In-Reply-To: <20261109.iej8biD4ohph@digikod.net>

On Mon, Nov 9, 2026 at 18:50:52 +0100, Mickaël Salaün wrote:
> This is directly visible with the new Landlock control of capabilities.


I reported the PSI/Landlock CAP_SYS_RESOURCE mismatch privately to
the maintainers on November 4, 2026, along with reproduction results.

I tested Hungyu's patch on Linux v7.4-rc1 with Landlock ABI 12 and
confirmed that privileged PSI trigger creation is rejected after
Landlock restricts CAP_SYS_RESOURCE.

Nice catch on the user-namespace issue as well. Using
file_ns_capable() with &init_user_ns restores both the initial user
namespace check and LSM mediation.

Reported-by: Sieun Yang <didtldms2525@jnu.ac.kr>
Tested-by: Sieun Yang <didtldms2525@jnu.ac.kr>

Thanks,
Sieun Yang

      reply	other threads:[~2026-11-10  0:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 12:00 Hungyu Lin
2026-11-09 17:50 ` Mickaël Salaün
2026-11-10  0:49   ` 양시은 [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=e360517ba7fa8262912a5c01b224ad9@cweb016.nm \
    --to=didtldms2525@naver.com \
    --cc=bsegall@google.com \
    --cc=cerasuolodomenico@gmail.com \
    --cc=dennylin0707@gmail.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=gnoack3000@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mic@digikod.net \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sashiko-bot@kernel.org \
    --cc=surenb@google.com \
    --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
all inboxes | Powered by JetHome®