mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Carlos Maiolino <cem@kernel.org>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: linux-fsdevel@vger.kernel.org, jack@suze.cz, djwong@kernel.org,
	 hch@lst.de, linux-security-module@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [RFC PATCH 3/4] xfs: replace ns_capable_noaudit()
Date: Fri, 24 Jul 2026 14:55:22 +0200	[thread overview]
Message-ID: <amNgjPELg6a3MBSs@andromeda.toxiclabs.cc> (raw)
In-Reply-To: <amIXSTSc47vQUOgk@mail.hallyn.com>

On Thu, Jul 23, 2026 at 08:29:45AM -0500, Serge E. Hallyn wrote:
> On Fri, Jun 26, 2026 at 01:45:22PM +0200, cem@kernel.org wrote:
> > From: Carlos Maiolino <cem@kernel.org>
> > 
> > We don't need to use ns_capable_noaudit() as all we care is the initial
> > user namespace, use capable_noaudit() instead.
> 
> Looks like some of your other xfs fixes conflict with this.  Do
> you mind sending out a new set, and I'll pull them into the caps-next
> branch?

I will Serge, thanks. I was hoping to send a new series this week but I
couldn't, and I'm out next week, so I'll come back to this in a couple
weeks.

Thanks for the heads up!

Carlos

> 
> thanks,
> -serge
> 
> > Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> > ---
> >  fs/xfs/xfs_trans_dquot.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/fs/xfs/xfs_trans_dquot.c b/fs/xfs/xfs_trans_dquot.c
> > index 50e5b323f7f1..30c2f6ec0aac 100644
> > --- a/fs/xfs/xfs_trans_dquot.c
> > +++ b/fs/xfs/xfs_trans_dquot.c
> > @@ -835,7 +835,7 @@ xfs_trans_dqresv(
> >  	if ((flags & XFS_QMOPT_FORCE_RES) == 0 &&
> >  	    dqp->q_id &&
> >  	    xfs_dquot_is_enforced(dqp) &&
> > -	    !ns_capable_noaudit(&init_user_ns, CAP_SYS_RESOURCE)) {
> > +	    !capable_noaudit(CAP_SYS_RESOURCE)) {
> >  		int		quota_nl;
> >  		bool		fatal;
> >  
> > -- 
> > 2.54.0

  reply	other threads:[~2026-07-24 12:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26 11:45 [RFC PATCH 0/4] Introduce capable_noaudit cem
2026-06-26 11:45 ` [RFC PATCH 1/4] capabily: Add new capable_noaudit cem
2026-06-26 15:16   ` Darrick J. Wong
2026-06-26 15:31   ` Paul Moore
2026-06-26 17:46     ` Serge E. Hallyn
2026-06-29 12:29   ` Christoph Hellwig
2026-06-29 13:49     ` Serge E. Hallyn
2026-07-02  7:53     ` Carlos Maiolino
2026-06-26 11:45 ` [RFC PATCH 2/4] quota: Don't issue audit messages on quota enforcing cem
2026-06-26 15:18   ` Darrick J. Wong
2026-06-29 12:30   ` Christoph Hellwig
2026-06-26 11:45 ` [RFC PATCH 3/4] xfs: replace ns_capable_noaudit() cem
2026-06-26 15:19   ` Darrick J. Wong
2026-06-29 12:30     ` Christoph Hellwig
2026-06-29 12:30   ` Christoph Hellwig
2026-07-23 13:29   ` Serge E. Hallyn
2026-07-24 12:55     ` Carlos Maiolino [this message]
2026-06-26 11:45 ` [RFC PATCH 4/4] capability: unexport has_capability_noaudit cem
2026-06-26 15:20   ` Darrick J. Wong
2026-06-29 12:31     ` Christoph Hellwig
2026-06-29 12:31   ` Christoph Hellwig
2026-07-02  7:41 ` [RFC PATCH 0/4] Introduce capable_noaudit Christian Brauner
2026-07-02  8:35   ` Carlos Maiolino
2026-07-02 13:47     ` Christian Brauner
2026-07-02 14:51       ` Carlos Maiolino

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=amNgjPELg6a3MBSs@andromeda.toxiclabs.cc \
    --to=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=jack@suze.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=serge@hallyn.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®