From: Jingbo Xu <jefflexu@linux.alibaba.com>
To: xiang@kernel.org, chao@kernel.org, huyue2@coolpad.com,
linux-erofs@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH v5 0/6] erofs: cleanup of xattr handling
Date: Thu, 1 Jun 2023 10:43:41 +0800 [thread overview]
Message-ID: <20230601024347.108469-1-jefflexu@linux.alibaba.com> (raw)
changes since v4:
- patch 1: make conversions from erofs_read_metabuf() in xattr.c
to "erofs_init_metabuf() + erofs_bread()" a separate patch
- patch 6: add "bool copy" function parameter to erofs_xattr_body(), and
thus make erofs_xattr_namematch() and erofs_xattr_copy() inlined
inside erofs_xattr_body()
changes since v3:
- patch 1: make a unified erofs_xattr_iter_fixup() API with newly
introduced "bool nospan" argument; call erofs_init_metabuf() and
erofs_bread() separately instead of erofs_read_metabuf()
- patch 2: avoid duplicated strlen() calculation in erofs_getxattr(); no
need zeroing other fields when initializing 'struct erofs_xattr_iter'
- patch 4: don't explode 'struct erofs_xattr_iter' with inode/getxattr
fields; instead pass inode/getxattr parameters through function
parameters of erofs_iter_[inline|shared]_xattr()
- patch 5: don't explode 'struct erofs_xattr_iter' with remaining field;
instead calculate and check the remaining inside
erofs_iter_inline_xattr()
changes since v2:
- rebase to v6.4-rc2
- passes xattr tests (erofs/019,020,021) of erofs-utils [1]
[1] https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git/log/?h=experimental-tests
v4: https://lore.kernel.org/all/20230531031330.3504-1-jefflexu@linux.alibaba.com/
v3: https://lore.kernel.org/lkml/20230518024551.123990-1-jefflexu@linux.alibaba.com/
v2: https://lore.kernel.org/all/20230330082910.125374-1-jefflexu@linux.alibaba.com/
v1: https://lore.kernel.org/all/20230323000949.57608-1-jefflexu@linux.alibaba.com/
Jingbo Xu (6):
erofs: convert erofs_read_metabuf() to erofs_bread() for xattr
erofs: enhance erofs_xattr_iter_fixup() helper
erofs: unify xattr_iter structures
erofs: make the size of read data stored in buffer_ofs
erofs: unify inline/share xattr iterators for listxattr/getxattr
erofs: use separate xattr parsers for listxattr/getxattr
fs/erofs/xattr.c | 673 ++++++++++++++++++-----------------------------
1 file changed, 254 insertions(+), 419 deletions(-)
--
2.19.1.6.gb485710b
next reply other threads:[~2023-06-01 2:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 2:43 Jingbo Xu [this message]
2023-06-01 2:43 ` [PATCH v5 1/6] erofs: convert erofs_read_metabuf() to erofs_bread() for xattr Jingbo Xu
2023-06-01 3:01 ` Gao Xiang
2023-06-01 2:43 ` [PATCH v5 2/6] erofs: enhance erofs_xattr_iter_fixup() helper Jingbo Xu
2023-06-01 3:03 ` Gao Xiang
2023-06-01 2:43 ` [PATCH v5 3/6] erofs: unify xattr_iter structures Jingbo Xu
2023-06-01 3:26 ` Gao Xiang
2023-06-01 2:43 ` [PATCH v5 4/6] erofs: make the size of read data stored in buffer_ofs Jingbo Xu
2023-06-01 3:29 ` Gao Xiang
2023-06-01 2:43 ` [PATCH v5 5/6] erofs: unify inline/share xattr iterators for listxattr/getxattr Jingbo Xu
2023-06-01 2:43 ` [PATCH v5 6/6] erofs: use separate xattr parsers " Jingbo Xu
2023-06-01 3:37 ` Gao Xiang
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=20230601024347.108469-1-jefflexu@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@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
all inboxes | Powered by JetHome®