From: cem@kernel.org
To: cem@kernel.org
Cc: jack@suse.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: [PATCH v4 5/5] capability: unexport has_capability_noaudit
Date: Tue, 4 Aug 2026 11:45:55 +0200 [thread overview]
Message-ID: <20260804094602.84766-6-cem@kernel.org> (raw)
In-Reply-To: <20260804094602.84766-1-cem@kernel.org>
From: Carlos Maiolino <cem@kernel.org>
This has been originally exported to be used in xfs. Giving we are not
using it anymore, unexport for consistency.
Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
---
kernel/capability.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/capability.c b/kernel/capability.c
index f4a7f1963c9d..90e6ab62f6db 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);
static bool ns_capable_common(struct user_namespace *ns,
int cap,
--
2.55.0
prev parent reply other threads:[~2026-08-04 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 9:45 [PATCH v4 0/5] Fix quota evasion on xfs and add capable_noaudit cem
2026-08-04 9:45 ` [PATCH v4 1/5] xfs: fix capability check in xfs cem
2026-08-04 14:08 ` Christoph Hellwig
2026-08-04 9:45 ` [PATCH v4 2/5] capability: Add new capable_noaudit cem
2026-08-04 9:45 ` [PATCH v4 3/5] quota: Don't issue audit messages on quota enforcing cem
2026-08-04 9:45 ` [PATCH v4 4/5] xfs: replace ns_capable_noaudit cem
2026-08-04 14:09 ` Christoph Hellwig
2026-08-04 9:45 ` cem [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=20260804094602.84766-6-cem@kernel.org \
--to=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--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