From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@redhat.com>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: allow SECURE namespace xattrs to use reserved pool
Date: Mon, 22 Jul 2024 08:11:43 -0700 [thread overview]
Message-ID: <Zp52r8TBTQjJP-M-@infradead.org> (raw)
In-Reply-To: <da41c7f5-8542-4b8e-9e98-2c33a74ca1a9@sandeen.net>
On Mon, Jul 22, 2024 at 10:05:03AM -0500, Eric Sandeen wrote:
> Ok, I thought the local var was a little prettier but *shrug* can do it
> either way.
>
> To be honest I'm not sure why it was done for ROOT; dchinnner mentioned
> something about DMAPI requirements, long ago...
>
> It seems reasonable, and it's been there forever but also not obviously
> required, AFAICT.
>
> What would your explanation be? ;)
Based on your explanation it's probably ACLs for the same reason it
applies to the security attributes.
next prev parent reply other threads:[~2024-07-22 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 22:48 [PATCH] xfs: allow SECURE namespace xattrs to use reserved pool Eric Sandeen
2024-07-22 14:41 ` Christoph Hellwig
2024-07-22 15:05 ` Eric Sandeen
2024-07-22 15:11 ` Christoph Hellwig [this message]
2024-07-22 16:43 ` [External] : " mark.tinguely
2024-07-22 22:45 ` Dave Chinner
2024-07-22 19:25 ` [PATCH V2] xfs: allow SECURE namespace xattrs to use reserved block pool Eric Sandeen
2024-07-22 23:05 ` Dave Chinner
2024-07-23 14:59 ` [PATCH V3] " Eric Sandeen
2024-07-23 16:52 ` Darrick J. Wong
2024-07-23 16:56 ` Christoph Hellwig
2024-07-23 17:26 ` [PATCH V4] " 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=Zp52r8TBTQjJP-M-@infradead.org \
--to=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
/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