From: An Long <lan@suse.com>
To: fstests@vger.kernel.org
Cc: An Long <lan@suse.com>
Subject: [PATCH] btrfs/315: update 315.out to adapt mount cmd
Date: Thu, 19 Sep 2024 01:07:53 +0800 [thread overview]
Message-ID: <bb85eb7d443b2da482b6087d8946f0efafa15f87.camel@suse.com> (raw)
Mount error info changed since util-linux v2.40
(91ea38e libmount: report failed syscall name).
So add "mount" before "system call failed".
Signed-off-by: An Long <lan@suse.com>
---
tests/btrfs/315.out | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/btrfs/315.out b/tests/btrfs/315.out
index 3ea7a35a..a19ae8d5 100644
--- a/tests/btrfs/315.out
+++ b/tests/btrfs/315.out
@@ -1,7 +1,7 @@
QA output created by 315
---- seed_device_must_fail ----
mount: SCRATCH_MNT: WARNING: source write-protected, mounted read-
only.
-mount: TEST_DIR/315/tempfsid_mnt: system call failed: File exists.
+mount: TEST_DIR/315/tempfsid_mnt: mount system call failed: File
exists.
---- device_add_must_fail ----
wrote 9000/9000 bytes at offset 0
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
--
2.43.0
next reply other threads:[~2024-09-18 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 17:07 An Long [this message]
2024-09-18 17:53 ` [PATCH] btrfs/315: update 315.out to adapt mount cmd Filipe Manana
2024-09-19 12:01 ` Zorro Lang
2024-09-20 10:12 ` Filipe Manana
2024-09-20 14:28 ` Zorro Lang
2024-09-23 4:45 ` An Long
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=bb85eb7d443b2da482b6087d8946f0efafa15f87.camel@suse.com \
--to=lan@suse.com \
--cc=fstests@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