From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4] syscalls/sync_file_range: add partial file sync test-cases
Date: Wed, 19 Jun 2019 11:58:05 +0200 [thread overview]
Message-ID: <20190619095805.GC16577@rei.lan> (raw)
In-Reply-To: <CAOQ4uxithmPn6J=B2kaGKT0JOpqzyVEkHU+zMqhXCYnnH+ZHVQ@mail.gmail.com>
Hi!
> > With these modification the test was stable and worked fine for more
> > than 100 iterations for me. It still fails for FUSE based filesystems
> > but that is to be expected since FUSE does not implement sync_file_range
> > yet.
> >
>
> What is the proposed way to resolve this failure?
> If FUSE does not implement sync_file_range, shouldn't test detect
> it and return TCONF?
Well the call returns success but does not sync anything on FUSE based
filesystems so the choices here are:
1) Disable the test of FUSE
2) Keep the test failing and ignore the failures
Which one do you prefer?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-06-19 9:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 10:13 [LTP] [PATCH v4] syscalls/sync_file_range: add partial file sync test-cases Sumit Garg
2019-06-10 12:04 ` Li Wang
2019-06-17 12:26 ` Sumit Garg
2019-06-17 13:06 ` Cyril Hrubis
2019-06-17 15:06 ` Cyril Hrubis
2019-06-18 15:49 ` Amir Goldstein
2019-06-19 9:58 ` Cyril Hrubis [this message]
2019-06-19 10:28 ` Amir Goldstein
2019-09-29 13:27 ` Caspar Zhang
2019-10-04 7:33 ` Sumit Garg
2019-10-16 2:54 ` Caspar Zhang
2019-10-16 6:23 ` Sumit Garg
2019-10-17 7:36 ` Caspar Zhang
2019-10-29 6:08 ` Naresh Kamboju
2019-10-30 9:45 ` Sumit Garg
2019-11-05 9:05 ` Naresh Kamboju
2019-10-30 9:40 ` Sumit Garg
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=20190619095805.GC16577@rei.lan \
--to=chrubis@suse.cz \
--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.