Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org, david@fromorbit.com
Subject: Re: [PATCH V2] xfs: add selinux labels to whiteout inodes
Date: Wed, 22 Jun 2022 18:41:10 -0500	[thread overview]
Message-ID: <f01f8d0c-1132-251b-b25d-d9dd72f119b2@redhat.com> (raw)
In-Reply-To: <YrOmLRfS0eIrMCDl@magnolia>

On 6/22/22 6:30 PM, Darrick J. Wong wrote:
> On Mon, Jun 20, 2022 at 08:38:36PM -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. Now that xfs_init_security is not static,
>> rename it to xfs_inode_init_security per dchinner's suggestion.
>>
>> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>> Reviewed-by: Dave Chinner <dchinner@redhat.com>
> 
> Looks fine to me.  I wondered slightly if the label creation needs to be
> atomic with the file creation, but quickly realized that /never/
> happens.  Assuming this isn't high priority 5.19 stuff, I'll just roll
> this into 5.20 if that's ok?
> 
> Reviewed-by: Darrick J. Wong <djwong@kernel.org>

Thanks Darrick. I don't think it's high priority, I got a bug report about
the behavior, but there was no indication that it was actively causing
visible problems.

-Eric


      reply	other threads:[~2022-06-22 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
2022-06-21  1:38 ` [PATCH V2] " Eric Sandeen
2022-06-22 23:30   ` Darrick J. Wong
2022-06-22 23:41     ` Eric Sandeen [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=f01f8d0c-1132-251b-b25d-d9dd72f119b2@redhat.com \
    --to=sandeen@redhat.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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