Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jingbo Xu <jefflexu@linux.alibaba.com>
To: xiang@kernel.org, chao@kernel.org, huyue2@coolpad.com,
	linux-erofs@lists.ozlabs.org
Subject: [PATCH 0/5] erofs-utils: tests: restructure test cases for xattr
Date: Thu, 25 May 2023 16:31:56 +0800	[thread overview]
Message-ID: <20230525083201.23740-1-jefflexu@linux.alibaba.com> (raw)

This series restructures some existing test cases for xattr.

- patch 1/2: some generic helpers are extracted from erofs/019 [1]
- patch 3/4: the previous posted test case [2] checking xattrs in
  different layouts are split into two test cases, i.e. erofs/020 and
  erofs/021.
    - erofs/020 checks xattrs in different layouts and is independent on
      the "-b#" feature of mkfs.erofs
    - erofs/021 checks xattrs crossing block boundary.  It is dependent
      on the "-b#" feature of mkfs.erofs and will "notrun" if mkfs.erofs
      doesn't support this feature yet
- patch 5: it's the previous posted test case [3] checking long xattr
  name prefixes, except that it will "notrun" if mkfs.erofs doesn't
  support "--xattr-prefix" feature yet

[1] https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git/tree/tests/erofs/019?h=experimental-tests
[2] https://lore.kernel.org/all/20230327123926.92934-1-jefflexu@linux.alibaba.com/
[3] https://lore.kernel.org/all/20230411103004.104064-1-jefflexu@linux.alibaba.com/

Huang Jianan (1):
  erofs-utils: tests: add test for xattrs

Jingbo Xu (4):
  erofs-utils: tests: add generic helper for xattrs
  erofs-utils: tests: add test for xattrs in different layouts
  erofs-utils: tests: add test for xattr crossing block boundary
  erofs-utils: tests: add test for long xattr name prefixes

 tests/Makefile.am   | 12 +++++++++
 tests/common/rc     | 44 ++++++++++++++++++++++++++++++
 tests/erofs/019     | 55 ++++++++++++++++++++++++++++++++++++++
 tests/erofs/019.out |  2 ++
 tests/erofs/020     | 77 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/erofs/020.out |  2 ++
 tests/erofs/021     | 60 +++++++++++++++++++++++++++++++++++++++++
 tests/erofs/021.out |  2 ++
 tests/erofs/022     | 77 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/erofs/022.out |  2 ++
 10 files changed, 333 insertions(+)
 create mode 100755 tests/erofs/019
 create mode 100644 tests/erofs/019.out
 create mode 100755 tests/erofs/020
 create mode 100644 tests/erofs/020.out
 create mode 100755 tests/erofs/021
 create mode 100644 tests/erofs/021.out
 create mode 100755 tests/erofs/022
 create mode 100644 tests/erofs/022.out

-- 
1.8.3.1


             reply	other threads:[~2023-05-25  8:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25  8:31 Jingbo Xu [this message]
2023-05-25  8:31 ` [PATCH 1/5] erofs-utils: tests: add generic helper for xattrs Jingbo Xu
2023-05-25  8:31 ` [PATCH 2/5] erofs-utils: tests: add test " Jingbo Xu
2023-05-25  8:31 ` [PATCH 3/5] erofs-utils: tests: add test for xattrs in different layouts Jingbo Xu
2023-05-25  8:32 ` [PATCH 4/5] erofs-utils: tests: add test for xattr crossing block boundary Jingbo Xu
2023-05-25  8:32 ` [PATCH 5/5] erofs-utils: tests: add test for long xattr name prefixes Jingbo Xu

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=20230525083201.23740-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=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