From: Andrey Albershteyn <aalbersh@redhat.com>
To: linux-xfs@vger.kernel.org, fstests@vger.kernel.org,
zlang@redhat.com, djwong@kernel.org, aalbersh@kernel.org
Subject: [PATCH v2 0/3] generic/772: split and fix
Date: Thu, 30 Oct 2025 16:30:09 +0100 [thread overview]
Message-ID: <cover.1761838171.patch-series@thinky> (raw)
Hi all,
This one add one missed file attribute flag (n). Then, the check for
file_getattr/file_setattr on regular and special files is lifted to the
common/ for futher test splitting. The generic/772 is split into two
tests one for regular files and one for special files.
This one based on top of Darrick's "random fixes" patchset [1]
Changes from v1:
- Remove patch which added file attribute as it's now convered
- Use TEST_DIR instead of depending on SCRATCH_MNT
To: fstests@vger.kernel.org
Cc: linux-xfs@vger.kernel.org
Cc: zlang@redhat.com
Cc: djwong@kernel.org
[1]: https://lore.kernel.org/fstests/176107188615.4163693.708102333699699249.stgit@frogsfrogsfrogs/
Andrey Albershteyn <aalbersh@kernel.org>:
generic/772: require filesystem to support file_[g|s]etattr
generic/772: split this test into 772 and 779 for regular and special files
common/rc | 32 ++++++++++++++++++++++++++++++++
tests/generic/772 | 41 ++---------------------------------------
tests/generic/772.out | 14 --------------
tests/generic/779 | 86 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/generic/779.out | 20 ++++++++++++++++++++
tests/xfs/648 | 6 ++----
6 files changed, 142 insertions(+), 57 deletions(-)
--
- Andrey
next reply other threads:[~2025-10-30 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 15:30 Andrey Albershteyn [this message]
2025-10-30 15:30 ` [PATCH v2 1/2] generic/772: require filesystem to support file_[g|s]etattr Andrey Albershteyn
2025-10-30 16:03 ` Darrick J. Wong
2025-11-01 9:11 ` Zorro Lang
2025-10-30 15:30 ` [PATCH v2 2/2] generic/772: split this test into 772 and 779 for regular and special files Andrey Albershteyn
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=cover.1761838171.patch-series@thinky \
--to=aalbersh@redhat.com \
--cc=aalbersh@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.