From: Andreas Dilger <adilger@dilger.ca>
To: Clay Harris <bugs@claycon.org>
Cc: Stefan Metzmacher <metze@samba.org>, Stefan Roesch <shr@fb.com>,
io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v1 0/5] io_uring: add xattr support
Date: Wed, 1 Dec 2021 13:05:54 -0700 [thread overview]
Message-ID: <A581A60C-E377-48BE-9D9E-DCD5155ED8BD@dilger.ca> (raw)
In-Reply-To: <20211201195239.mlgb4qwj2hk2d3tv@ps29521.dreamhostps.com>
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
On Dec 1, 2021, at 12:52 PM, Clay Harris <bugs@claycon.org> wrote:
>
> On Wed, Dec 01 2021 at 13:19:03 +0100, Stefan Metzmacher quoth thus:
>>
>> What's with lsetxattr and lgetxattr, why are they missing.
> Do any filesystems even support xattrs on symbolic links?
Yes, ext4 does. There are definitely security xattrs on symlinks that
need to be accessed and changed.
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
next prev parent reply other threads:[~2021-12-01 20:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 22:12 [PATCH v1 0/5] io_uring: add xattr support Stefan Roesch
2021-11-29 22:12 ` [PATCH v1 1/5] fs: make user_path_at_empty() take a struct filename Stefan Roesch
2021-11-30 2:09 ` kernel test robot
2021-11-29 22:12 ` [PATCH v1 2/5] fs: split off setxattr_setup function from setxattr Stefan Roesch
2021-11-29 22:12 ` [PATCH v1 3/5] fs: split off the vfs_getxattr from getxattr Stefan Roesch
2021-11-30 13:40 ` [fs] 23a831cdec: WARNING:at_include/linux/thread_info.h:#do_getxattr kernel test robot
2021-11-29 22:12 ` [PATCH v1 4/5] io_uring: add fsetxattr and setxattr support Stefan Roesch
2021-11-29 22:12 ` [PATCH v1 5/5] io_uring: add fgetxattr and getxattr support Stefan Roesch
2021-11-30 1:08 ` [PATCH v1 0/5] io_uring: add xattr support Clay Harris
2021-11-30 3:16 ` Andreas Dilger
2021-11-30 6:37 ` Clay Harris
2021-11-30 6:53 ` Clay Harris
2021-11-30 11:40 ` Clay Harris
2021-11-30 7:19 ` Dave Chinner
2021-12-01 6:16 ` Stefan Roesch
2021-12-01 6:07 ` Stefan Roesch
2021-12-01 7:46 ` Clay Harris
2021-12-01 13:14 ` Christian Brauner
2021-12-01 12:19 ` Stefan Metzmacher
2021-12-01 19:52 ` Clay Harris
2021-12-01 20:05 ` Andreas Dilger [this message]
2021-12-03 17:58 ` Stefan Roesch
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=A581A60C-E377-48BE-9D9E-DCD5155ED8BD@dilger.ca \
--to=adilger@dilger.ca \
--cc=bugs@claycon.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=metze@samba.org \
--cc=shr@fb.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;
as well as URLs for NNTP newsgroup(s).