From: "Darrick J. Wong" <djwong@kernel.org>
To: cem@kernel.org
Cc: linux-fsdevel@vger.kernel.org, jack@suze.cz, 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 4/4] capability: unexport has_capability_noaudit
Date: Fri, 26 Jun 2026 08:20:08 -0700 [thread overview]
Message-ID: <20260626152008.GW6078@frogsfrogsfrogs> (raw)
In-Reply-To: <20260626114533.102138-5-cem@kernel.org>
On Fri, Jun 26, 2026 at 01:45:23PM +0200, cem@kernel.org wrote:
> From: Carlos Maiolino <cem@kernel.org>
>
> This has been originally exported to be used in xfs. Givin we are not
> using it anymore, unexport for consistency.
>
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
> kernel/capability.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/kernel/capability.c b/kernel/capability.c
> index 2c2d1e8300bd..3d0387fb93a3 100644
> --- a/kernel/capability.c
> +++ b/kernel/capability.c
> @@ -326,7 +326,6 @@ bool has_capability_noaudit(struct task_struct *t, int cap)
> {
> return has_ns_capability_noaudit(t, &init_user_ns, cap);
> }
> -EXPORT_SYMBOL(has_capability_noaudit);
Please update the kerneldoc for this function to mention that it only
checks real capability, not effective capability. I'd like to prevent
someone else from making the same mistakes I did with these functions
that sound the same in documentation but have very different behaviors.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
>
> static bool ns_capable_common(struct user_namespace *ns,
> int cap,
> --
> 2.54.0
>
>
prev parent reply other threads:[~2026-06-26 15:20 UTC|newest]
Thread overview: 11+ 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-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-26 11:45 ` [RFC PATCH 3/4] xfs: replace ns_capable_noaudit() cem
2026-06-26 15:19 ` Darrick J. Wong
2026-06-26 11:45 ` [RFC PATCH 4/4] capability: unexport has_capability_noaudit cem
2026-06-26 15:20 ` Darrick J. Wong [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=20260626152008.GW6078@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@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 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.