From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: add selinux labels to whiteout inodes
Date: Tue, 21 Jun 2022 09:41:29 +1000 [thread overview]
Message-ID: <20220620234129.GN227878@dread.disaster.area> (raw)
In-Reply-To: <1655765731-21078-1-git-send-email-sandeen@redhat.com>
On Mon, Jun 20, 2022 at 05:55:31PM -0500, Eric Sandeen wrote:
> We got a report that "renameat2() with flags=RENAME_WHITEOUT doesn't
> apply an SELinux label on xfs" as it does on other filesystems
> (for example, ext4 and tmpfs.) While I'm not quite sure how labels
> may interact w/ whiteout files, leaving them as unlabeled seems
> inconsistent at best.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
> fs/xfs/xfs_inode.c | 14 +++++++++++++-
> fs/xfs/xfs_iops.c | 2 +-
> fs/xfs/xfs_iops.h | 3 +++
> 3 files changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> index 52d6f2c..9a43060 100644
> --- a/fs/xfs/xfs_inode.c
> +++ b/fs/xfs/xfs_inode.c
> @@ -3046,10 +3046,12 @@ struct xfs_iunlink {
> static int
> xfs_rename_alloc_whiteout(
> struct user_namespace *mnt_userns,
> + struct xfs_name *src_name,
> struct xfs_inode *dp,
> struct xfs_inode **wip)
> {
> struct xfs_inode *tmpfile;
> + struct qstr name;
> int error;
>
> error = xfs_create_tmpfile(mnt_userns, dp, S_IFCHR | WHITEOUT_MODE,
> @@ -3057,6 +3059,15 @@ struct xfs_iunlink {
> if (error)
> return error;
>
> + name.name = src_name->name;
> + name.len = src_name->len;
> + error = xfs_init_security(VFS_I(tmpfile), VFS_I(dp), &name);
> + if (error) {
> + xfs_finish_inode_setup(tmpfile);
> + xfs_irele(tmpfile);
> + return error;
> + }
> +
I was worried that this would be inside an existing transaction,
but the tmpfile create is outside the rename transaction so this
will be fine.
> /*
> * Prepare the tmpfile inode as if it were created through the VFS.
> * Complete the inode setup and flag it as linkable. nlink is already
> @@ -3107,7 +3118,8 @@ struct xfs_iunlink {
> * appropriately.
> */
> if (flags & RENAME_WHITEOUT) {
> - error = xfs_rename_alloc_whiteout(mnt_userns, target_dp, &wip);
> + error = xfs_rename_alloc_whiteout(mnt_userns, src_name,
> + target_dp, &wip);
> if (error)
> return error;
>
> diff --git a/fs/xfs/xfs_iops.c b/fs/xfs/xfs_iops.c
> index 29f5b8b8..c7775b7 100644
> --- a/fs/xfs/xfs_iops.c
> +++ b/fs/xfs/xfs_iops.c
> @@ -76,7 +76,7 @@
> * inode, of course, such that log replay can't cause these to be lost).
> */
>
> -STATIC int
> +int
> xfs_init_security(
This function needs renaming, though. As a static function it can
get away with not having a namespace, but as a globally visible
function it needs to have an "xfs_inode_" prefix....
Otherwise OK.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-06-20 23:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 22:55 [PATCH] xfs: add selinux labels to whiteout inodes Eric Sandeen
2022-06-20 23:06 ` Eric Sandeen
2022-06-20 23:41 ` Dave Chinner [this message]
2022-06-21 1:38 ` [PATCH V2] " Eric Sandeen
2022-06-22 23:30 ` Darrick J. Wong
2022-06-22 23:41 ` Eric Sandeen
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=20220620234129.GN227878@dread.disaster.area \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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