From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] safe_mount: Do not try mount() syscall for FUSE fs
Date: Wed, 17 Jan 2018 03:54:18 -0500 (EST) [thread overview]
Message-ID: <1990718613.918376.1516179258863.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180116092318.20521-1-chrubis@suse.cz>
----- Original Message -----
> The problem here is that there exists two NTFS implementations. There is
> a readonly support in the kernel and full read/write FUSE
> implementation. If there is a NTFS kernel module present on the system
> the mount() syscall successfuly mounts the device in read-only mode
> which causes the tests to fail once they attempt to create a file.
>
> Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
This would prevent test using read-only kernel version of NTFS,
but no such test exists (and EROFS tests use tmpfs).
ACK
Regards,
Jan
next prev parent reply other threads:[~2018-01-17 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 9:23 [LTP] [PATCH] safe_mount: Do not try mount() syscall for FUSE fs Cyril Hrubis
2018-01-17 8:54 ` Jan Stancek [this message]
2018-01-17 14:59 ` Cyril Hrubis
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=1990718613.918376.1516179258863.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox