From: ChenXiaoSong <chenxiaosong@chenxiaosong.com>
To: smfrench@gmail.com, linkinjeon@kernel.org, pc@manguebit.org,
ronniesahlberg@gmail.com, sprasad@microsoft.com, tom@talpey.com,
bharathsm@microsoft.com, senozhatsky@chromium.org,
dhowells@redhat.com, metze@samba.org, hch@infradead.org,
zlang@kernel.org
Cc: linux-cifs@vger.kernel.org,
ChenXiaoSong <chenxiaosong@kylinos.cn>,
Christoph Hellwig <hch@lst.de>
Subject: [PATCH v4 1/2] generic/002: add test to hardlink group
Date: Thu, 30 Jul 2026 02:12:37 +0000 [thread overview]
Message-ID: <20260730021238.51634-2-chenxiaosong@chenxiaosong.com> (raw)
In-Reply-To: <20260730021238.51634-1-chenxiaosong@chenxiaosong.com>
From: ChenXiaoSong <chenxiaosong@kylinos.cn>
The test creates and removes hard links, so add it to the hardlink
group.
Suggested-by: Zorro Lang <zlang@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: ChenXiaoSong <chenxiaosong@kylinos.cn>
---
tests/generic/002 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/generic/002 b/tests/generic/002
index 6df57a7a..a0773e22 100755
--- a/tests/generic/002
+++ b/tests/generic/002
@@ -7,7 +7,7 @@
# simple inode link count test for a regular file
#
. ./common/preamble
-_begin_fstest metadata udf auto quick
+_begin_fstest metadata udf auto quick hardlink
# Import common functions.
. ./common/filter
--
2.43.0
next prev parent reply other threads:[~2026-07-30 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 2:12 [PATCH v4 0/2] generic: new test to check nlink returned by fstat() ChenXiaoSong
2026-07-30 2:12 ` ChenXiaoSong [this message]
2026-08-03 10:44 ` [PATCH v4 1/2] generic/002: add test to hardlink group Zorro Lang
2026-07-30 2:12 ` [PATCH v4 2/2] generic: new test to check nlink returned by fstat() ChenXiaoSong
2026-08-03 10:40 ` Zorro Lang
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=20260730021238.51634-2-chenxiaosong@chenxiaosong.com \
--to=chenxiaosong@chenxiaosong.com \
--cc=bharathsm@microsoft.com \
--cc=chenxiaosong@kylinos.cn \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=metze@samba.org \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.com \
--cc=zlang@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 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.