From: Anand Jain <anand.jain@oracle.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] fstests: new testcase to verify show_devname.
Date: Tue, 20 May 2025 16:28:33 +0800 [thread overview]
Message-ID: <cover.1747729098.git.anand.jain@oracle.com> (raw)
Mismatch causes mount -a (UUID) to fail with -EBUSY in libmount 2.37.4.
In libmount 2.40.2 with Btrfs, it shows 'successfully mounted' instead
of 'already mounted', kernel without fix.
Anand Jain (2):
fstests: new test case to verify show_devname() device path
fstests: btrfs: new test: show_devname() on multi-device volumes
tests/btrfs/329 | 107 ++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/329.out | 19 ++++++++
tests/generic/765 | 74 +++++++++++++++++++++++++++++
tests/generic/765.out | 6 +++
4 files changed, 206 insertions(+)
create mode 100755 tests/btrfs/329
create mode 100644 tests/btrfs/329.out
create mode 100755 tests/generic/765
create mode 100644 tests/generic/765.out
--
2.49.0
next reply other threads:[~2025-05-20 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 8:28 Anand Jain [this message]
2025-05-20 8:28 ` [PATCH 1/2] fstests: new test case to verify show_devname() device path Anand Jain
2025-05-20 8:28 ` [PATCH 2/2] fstests: btrfs: new test: show_devname() on multi-device volumes Anand Jain
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.1747729098.git.anand.jain@oracle.com \
--to=anand.jain@oracle.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