Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sheng Yong via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: linux-erofs@lists.ozlabs.org
Subject: Re: [RFC PATCH 2/3] erofs-utils: fuse: export erofs_xattr_foreach
Date: Tue, 9 Aug 2022 12:18:34 +0800	[thread overview]
Message-ID: <76efd3fa-e760-8321-8bb7-c7cc1daa9fe1@oppo.com> (raw)
In-Reply-To: <YvHbZrYUU7qDP0Jg@B-P7TQMD6M-0146.local>



在 2022/8/9 11:58, Gao Xiang 写道:
> Hi Yong,
>
> On Thu, Aug 04, 2022 at 03:46:24AM +0800, Gao Xiang wrote:
>>
>> On Wed, Aug 03, 2022 at 10:22:22PM +0800, Sheng Yong wrote:
>>> This patch exports erofs_xattr_foreach() to iterate all xattrs.
>>> Each xattr entry is handled by operations defined in `struct
>>> xattr_iter_ops'.
>>>
>>
>> Thanks for your hard effort!
>>
>> Could we import in-kernel xattr implementation with verify enabled
>> (or unify these implementations) instead?
>>
>> ( Jianan ported a kernel implementation before, could we enhance
>>    it with verification?
>>    https://lore.kernel.org/r/20220728120910.61636-1-jnhuang@linux.alibaba.com)
>>
>
> We're about to fix FUSE extended attribute support... Would you mind
> leaving your opinion about this?

Hi, Xiang

Sorry for late. At first glance, I though it would be too heavy to port
in-kernel code when I tried to add xattr to fuse client. But if we want
a more unified implementation and Jianan has already done it. I'd like
to try Jianan's version :-)

Thanks,
Sheng Yong

>
> Thanks,
> Gao Xiang
>
>> Thanks,
>> Gao Xiang
________________________________
OPPO

本电子邮件及其附件含有OPPO公司的保密信息,仅限于邮件指明的收件人使用(包含个人及群组)。禁止任何人在未经授权的情况下以任何形式使用。如果您错收了本邮件,请立即以电子邮件通知发件人并删除本邮件及其附件。

This e-mail and its attachments contain confidential information from OPPO, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

  reply	other threads:[~2022-08-09  4:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 14:22 [RFC PATCH 0/3] erofs-utils: fuse: support get/list xattr Sheng Yong via Linux-erofs
2022-08-03 14:22 ` [RFC PATCH 1/3] erofs-utils: fuse: set d_type for readdir Sheng Yong via Linux-erofs
2022-08-03 19:43   ` Gao Xiang
2022-08-04 15:02     ` Gao Xiang
2022-08-04 15:14       ` Sheng Yong via Linux-erofs
2022-08-07  8:08         ` [PATCH v2] " Sheng Yong
2022-08-07 10:26           ` Chao Yu
2022-08-08  1:59             ` Gao Xiang
2022-08-03 14:22 ` [RFC PATCH 2/3] erofs-utils: fuse: export erofs_xattr_foreach Sheng Yong via Linux-erofs
2022-08-03 19:46   ` Gao Xiang
2022-08-09  3:58     ` Gao Xiang
2022-08-09  4:18       ` Sheng Yong via Linux-erofs [this message]
2022-08-09  4:27         ` Gao Xiang
2022-08-03 14:22 ` [RFC PATCH 3/3] erofs-utils: fuse: support get/list xattr Sheng Yong via Linux-erofs

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=76efd3fa-e760-8321-8bb7-c7cc1daa9fe1@oppo.com \
    --to=linux-erofs@lists.ozlabs.org \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=shengyong@oppo.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