Linux Security Modules development
 help / color / mirror / Atom feed
From: Carlos Maiolino <cem@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, jack@suze.cz, djwong@kernel.org,
	 hch@lst.de, serge@hallyn.com,
	linux-security-module@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [RFC PATCH 0/4] Introduce capable_noaudit
Date: Thu, 2 Jul 2026 10:35:20 +0200	[thread overview]
Message-ID: <akYimPrAcHlv7shR@nidhogg.toxiclabs.cc> (raw)
In-Reply-To: <20260702-alufelgen-belag-tastatur-b666a49f7fc0@brauner>

On Thu, Jul 02, 2026 at 09:41:39AM +0200, Christian Brauner wrote:
> On 2026-06-26 13:45 +0200, cem@kernel.org wrote:
> > From: Carlos Maiolino <cem@kernel.org>
> > 
> > In some cases - filesystems quota specifically here - we'd like to check
> > for effective capabilities without issuing spurious audit messages and
> > without the need to specify a namespace for that.
> > 
> > This series introduce capable_noaudit() which has the same goal as
> > capable() but without firing audit messages.
> > 
> > Also, this updates both generic quota and xfs quota code to use that.
> > 
> > The last patch unexports has_capability_noaudit() which was originally
> > exported to be used in xfs but turns out it does not meet our needs.
> > 
> > Note this is based on top of a current series I have to remove
> > has_capability_noaudit() calls from xfs so the xfs patch won't
> > apply cleanly without that series.
> > 
> > If adding this helper is acceptable, I'll turn this into a non-rfc
> > series with the required changes to apply properly.
> > 
> > Comments? Flames?
> 
> Convert more, please.
> 

Convert what? :) more callers from capable() to capable_noaudit()?

  reply	other threads:[~2026-07-02  8:35 UTC|newest]

Thread overview: 22+ 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-06-26 11:45 ` [RFC PATCH 4/4] capability: unexport has_capability_noaudit cem
2026-06-29 12:31   ` Christoph Hellwig
     [not found]   ` <20260626152008.GW6078@frogsfrogsfrogs>
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 [this message]
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=akYimPrAcHlv7shR@nidhogg.toxiclabs.cc \
    --to=cem@kernel.org \
    --cc=brauner@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