[LTP] [PATCH v3] syscalls/sync_file_range: add partial file sync test-cases
Li Wang
liwang@redhat.com
Mon Apr 1 08:54:08 CEST 2019
Hi Sumit,
On Thu, Mar 7, 2019 at 8:44 PM Sumit Garg <sumit.garg@linaro.org> wrote:
> Add partial file sync tests as part of sync_file_range02 test-case.
>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> ---
>
> Changes in v3:
> 1. Add upper bound check for synced size to device.
> 2. Refactor tests for more code reuse.
> 3. Add another test to check sync over partial write.
>
> Changes in v2:
> 1. Do full file write instead of partial and test sync partial file.
>
> .../syscalls/sync_file_range/sync_file_range02.c | 47
> +++++++++++++++++-----
> 1 file changed, 37 insertions(+), 10 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/sync_file_range/sync_file_range02.c
> b/testcases/kernel/syscalls/sync_file_range/sync_file_range02.c
> index 82d77f7..334ea5e 100644
> --- a/testcases/kernel/syscalls/sync_file_range/sync_file_range02.c
> +++ b/testcases/kernel/syscalls/sync_file_range/sync_file_range02.c
> @@ -22,23 +22,36 @@
> #include "check_sync_file_range.h"
>
> #define MNTPOINT "mnt_point"
> -#define FNAME MNTPOINT"/test"
> -#define FILE_SIZE_MB 32
> -#define FILE_SIZE (FILE_SIZE_MB * TST_MB)
> +#define FNAME1 MNTPOINT"/test1"
> +#define FNAME2 MNTPOINT"/test2"
> +#define FNAME3 MNTPOINT"/test3"
> +#define FILE_SZ_MB 32
> +#define FILE_SZ (FILE_SZ_MB * TST_MB)
> #define MODE 0644
>
> -static void verify_sync_file_range(void)
> +struct testcase {
> + char *fname;
> + off64_t sync_off;
> + off64_t sync_size;
> + size_t exp_sync_size;
> + off64_t write_off;
> + size_t write_size_mb;
> +};
> +
> +static void verify_sync_file_range(struct testcase *tc)
> {
> int fd;
> unsigned long written;
>
> - fd = SAFE_OPEN(FNAME, O_RDWR|O_CREAT, MODE);
> + fd = SAFE_OPEN(tc->fname, O_RDWR|O_CREAT, MODE);
> +
> + lseek(fd, tc->write_off, SEEK_SET);
>
> tst_dev_bytes_written(tst_device->dev);
>
> - tst_fill_fd(fd, 0, TST_MB, FILE_SIZE_MB);
> + tst_fill_fd(fd, 0, TST_MB, tc->write_size_mb);
>
I'm just thinking that is probably more precise if we reverse the order of
tst_fill_fd() and tst_dev_bytes_written()? Because that does counting the
dev_bytes_writen only before and after sync_file_range(), we cann't
garantee system does not wirte back to deviece when do fill_fd(), isn't it?
>
> - TEST(sync_file_range(fd, 0, FILE_SIZE,
> + TEST(sync_file_range(fd, tc->sync_off, tc->sync_size,
> SYNC_FILE_RANGE_WAIT_BEFORE |
> SYNC_FILE_RANGE_WRITE |
> SYNC_FILE_RANGE_WAIT_AFTER));
> @@ -50,10 +63,23 @@ static void verify_sync_file_range(void)
>
> SAFE_CLOSE(fd);
>
> - if (written >= FILE_SIZE)
> + if ((written >= tc->exp_sync_size) &&
> + (written <= (tc->exp_sync_size + tc->exp_sync_size/10)))
> tst_res(TPASS, "Test file range synced to device");
> else
> - tst_res(TFAIL, "Synced %li, expected %i", written,
> FILE_SIZE);
> + tst_res(TFAIL, "Synced %li, expected %li", written,
> + tc->exp_sync_size);
> +}
> +
> +static struct testcase testcases[] = {
> + { FNAME1, 0, FILE_SZ, FILE_SZ, 0, FILE_SZ_MB },
> + { FNAME2, FILE_SZ/4, FILE_SZ/2, FILE_SZ/2, 0, FILE_SZ_MB },
> + { FNAME3, FILE_SZ/4, FILE_SZ/2, FILE_SZ/4, FILE_SZ/2, FILE_SZ_MB/4
> },
> +};
> +
> +static void run(unsigned int i)
> +{
> + verify_sync_file_range(&testcases[i]);
> }
>
> static void setup(void)
> @@ -63,10 +89,11 @@ static void setup(void)
> }
>
> static struct tst_test test = {
> + .tcnt = ARRAY_SIZE(testcases),
> .needs_root = 1,
> .mount_device = 1,
> .all_filesystems = 1,
> .mntpoint = MNTPOINT,
> .setup = setup,
> - .test_all = verify_sync_file_range,
> + .test = run,
> };
> --
> 2.7.4
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
>
--
Regards,
Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20190401/2c6a5a02/attachment.html>
More information about the ltp
mailing list