From: Jan Polensky <japo@linux.ibm.com>
To: ltp@lists.linux.it (Linux Test Project)
Subject: [LTP] [PATCH v3 1/1] safe_macros.c: Fix missing ro flag for FUSE mounts
Date: Tue, 29 Jul 2025 15:27:31 +0200 [thread overview]
Message-ID: <20250729132731.57978-1-japo@linux.ibm.com> (raw)
The test incorrectly assumes that FUSE mounts are read-only, but the mount
command does not explicitly set the read-only flag. As a result, the test fails
when checking `sb_flags` against `MS_RDONLY`.
Old behavior:
sudo LTP_SINGLE_FS_TYPE=ntfs strace -e trace=mount,statmount -o log.log -s 128 -f ./statmount02
...
statmount02.c:47: TFAIL: st_mount->sb_flags (0) != MS_RDONLY (1)
...
Relevant log excerpt:
3890601 mount("/dev/zero", "/tmp/mountBDSEqk", "ntfs", 0, NULL) = -1 ENOTBLK (Block device required)
3890608 mount("/dev/loop0", "/tmp/LTP_staTPRruR/mntpoint", "fuseblk", 0, "allow_other,blksize=4096,fd=4,rootmode=40000,user_id=0,group_id=0") = 0
3890607 statmount({size=24, mnt_id=0x80010957, param=STATMOUNT_SB_BASIC}, {size=512, mask=STATMOUNT_SB_BASIC, sb_dev_major=7, sb_dev_minor=0, sb_magic=FUSE_SUPER_MAGIC, sb_flags=0}, 512, 0) = 0
Reviewed-by: Avinesh Kumar <akumar@suse.de>
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Signed-off-by: Jan Polensky <japo@linux.ibm.com>
---
Change since v1 (Thanks Cyril & thanks for the ping):
* Removed restriction for NTFS.
Change since v2 (Thanks Avinesh):
* Changed commit title from: "Fix missing ro flag for FUSE NTFS mounts"
lib/safe_macros.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/lib/safe_macros.c b/lib/safe_macros.c
index d52b55ab70fe..25fad4b7cae0 100644
--- a/lib/safe_macros.c
+++ b/lib/safe_macros.c
@@ -945,10 +945,15 @@ int safe_mount(const char *file, const int lineno, void (*cleanup_fn)(void),
tst_resm_(file, lineno, TINFO, "tst_is_fuse: %d", tst_is_fuse(source));
if (possibly_fuse(filesystemtype)) {
char buf[1024];
+ const char* mount_fmt;
tst_resm_(file, lineno, TINFO, "Trying FUSE...");
- snprintf(buf, sizeof(buf), "mount.%s '%s' '%s'",
- filesystemtype, source, target);
+ if (mountflags == MS_RDONLY)
+ mount_fmt = "mount.%s -o ro '%s' '%s'";
+ else
+ mount_fmt = "mount.%s '%s' '%s'";
+ snprintf(buf, sizeof(buf), mount_fmt, filesystemtype,
+ source, target);
rval = tst_system(buf);
tst_resm_(file, lineno, TINFO, "tst_is_fuse: %d", tst_is_fuse(source));
--
2.50.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2025-07-29 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 13:27 Jan Polensky [this message]
2025-08-05 11:52 ` [LTP] [PATCH v3 1/1] safe_macros.c: Fix missing ro flag for FUSE mounts Petr Vorel
2025-08-05 11:57 ` Cyril Hrubis
2025-08-06 11:38 ` Jan Polensky
2025-08-05 11:54 ` Petr Vorel
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=20250729132731.57978-1-japo@linux.ibm.com \
--to=japo@linux.ibm.com \
--cc=ltp@lists.linux.it \
/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.