From: sergeh@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: Re: [PATCH v4 4/5] xfs: replace ns_capable_noaudit
Date: Thu, 6 Aug 2026 16:11:07 -0500 [thread overview]
Message-ID: <anT4a9F1izXTl5TG@AUS2MQ6190Y76.amd.com> (raw)
In-Reply-To: <20260804094602.84766-5-cem@kernel.org>
On Tue, Aug 04, 2026 at 11:45:54AM +0200, cem@kernel.org wrote:
> From: Carlos Maiolino <cem@kernel.org>
>
> Now that capable_noaudit() is available, we don't need to keep
> using ns_capable_noaudit() and specifying the usernaspace every single
(typo - usernaspace)
> time.
>
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
> V4: Fix indentation on xfs_ioctl_setattr_get_trans() changes
>
> fs/xfs/xfs_fsmap.c | 3 +--
> fs/xfs/xfs_ioctl.c | 2 +-
> fs/xfs/xfs_iops.c | 2 +-
> 3 files changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/fs/xfs/xfs_fsmap.c b/fs/xfs/xfs_fsmap.c
> index 7c79fbe0a74c..041bb2105ec6 100644
> --- a/fs/xfs/xfs_fsmap.c
> +++ b/fs/xfs/xfs_fsmap.c
> @@ -1174,8 +1174,7 @@ xfs_getfsmap(
> if (!xfs_getfsmap_check_keys(&head->fmh_keys[0], &head->fmh_keys[1]))
> return -EINVAL;
>
> - use_rmap = xfs_has_rmapbt(mp) &&
> - ns_capable_noaudit(&init_user_ns, CAP_SYS_ADMIN);
> + use_rmap = xfs_has_rmapbt(mp) && capable_noaudit(CAP_SYS_ADMIN);
> head->fmh_entries = 0;
>
> /* Set up our device handlers. */
> diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
> index 1a8af827dde1..96ca3e480cb9 100644
> --- a/fs/xfs/xfs_ioctl.c
> +++ b/fs/xfs/xfs_ioctl.c
> @@ -647,7 +647,7 @@ xfs_ioctl_setattr_get_trans(
> goto out_error;
>
> error = xfs_trans_alloc_ichange(ip, NULL, NULL, pdqp,
> - ns_capable_noaudit(&init_user_ns, CAP_FOWNER), &tp);
> + capable_noaudit(CAP_FOWNER), &tp);
> if (error)
> goto out_error;
>
> diff --git a/fs/xfs/xfs_iops.c b/fs/xfs/xfs_iops.c
> index 7a8c77fdcf68..3f36d6e7b917 100644
> --- a/fs/xfs/xfs_iops.c
> +++ b/fs/xfs/xfs_iops.c
> @@ -835,7 +835,7 @@ xfs_setattr_nonsize(
> }
>
> error = xfs_trans_alloc_ichange(ip, udqp, gdqp, NULL,
> - ns_capable_noaudit(&init_user_ns, CAP_FOWNER), &tp);
> + capable_noaudit(CAP_FOWNER), &tp);
> if (error)
> goto out_dqrele;
>
> --
> 2.55.0
>
next prev parent reply other threads:[~2026-08-06 21:11 UTC|newest]
Thread overview: 15+ 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-06 17:22 ` sergeh
2026-08-04 9:45 ` [PATCH v4 2/5] capability: Add new capable_noaudit cem
2026-08-06 18:49 ` sergeh
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-06 21:11 ` sergeh [this message]
2026-08-07 10:04 ` Carlos Maiolino
2026-08-04 9:45 ` [PATCH v4 5/5] capability: unexport has_capability_noaudit cem
2026-08-06 18:54 ` sergeh
2026-08-07 9:56 ` Carlos Maiolino
2026-08-06 21:09 ` [PATCH v4 0/5] Fix quota evasion on xfs and add capable_noaudit sergeh
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=anT4a9F1izXTl5TG@AUS2MQ6190Y76.amd.com \
--to=sergeh@kernel.org \
--cc=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 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.