From: Anand Jain <anajain.sg@gmail.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] fstests: test device reappearance with new maj:min
Date: Thu, 18 Sep 2025 08:32:45 +0800 [thread overview]
Message-ID: <cover.1758148804.git.anand.jain@oracle.com> (raw)
From: Anand Jain <anand.jain@oracle.com>
Tests filesystem behavior when a device reappears with a different
MAJ:MIN after a block layer transport failure.
Anand Jain (2):
common/rc: helper functions to handle block devices via sysfs
generic: test case for reappearing device
common/rc | 26 ++++++++++++++++
tests/generic/809 | 72 +++++++++++++++++++++++++++++++++++++++++++
tests/generic/809.out | 2 ++
3 files changed, 100 insertions(+)
create mode 100755 tests/generic/809
create mode 100644 tests/generic/809.out
--
2.51.0
next reply other threads:[~2025-09-18 0:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 0:32 Anand Jain [this message]
2025-09-18 0:32 ` [PATCH 1/2] common/rc: helper functions to handle block devices via sysfs Anand Jain
2025-09-26 15:57 ` Zorro Lang
2025-09-30 3:47 ` Anand Jain
2025-09-18 0:32 ` [PATCH 2/2] generic: test case for reappearing device Anand Jain
2025-09-18 17:15 ` [PATCH 0/2] fstests: test device reappearance with new maj:min Neal Gompa
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.1758148804.git.anand.jain@oracle.com \
--to=anajain.sg@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.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;
as well as URLs for NNTP newsgroup(s).