From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 1/6] syscalls/readahead02: Convert to newlib and cleanup
Date: Mon, 3 Dec 2018 15:39:34 +0100 [thread overview]
Message-ID: <20181203143934.GB4974@rei.lan> (raw)
In-Reply-To: <20181128164645.783-2-amir73il@gmail.com>
Hi!
> +static struct tst_test test = {
> + .needs_root = 1,
> + .needs_tmpdir = 1,
> + .mount_device = 1,
> + .mntpoint = mntpoint,
> + .setup = setup,
> + .options = options,
> + .test_all = test_readahead,
> +};
I do wonder if it makes sense to set the all_filesystems flag now.
Also does it make any sense to run the overlay test against all
filesystems? I would expect that it does not, so we will have to figure
out how to run the tests. Maybe it would make most sense to treat the
overlayfs as another filesystem in all_filesystem tests...
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-12-03 14:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 16:46 [LTP] [PATCH v4 0/6] Tests for readahead() and fadvise() on overlayfs Amir Goldstein
2018-11-28 16:46 ` [LTP] [PATCH v4 1/6] syscalls/readahead02: Convert to newlib and cleanup Amir Goldstein
2018-12-03 14:39 ` Cyril Hrubis [this message]
2018-12-03 14:59 ` Amir Goldstein
2018-11-28 16:46 ` [LTP] [PATCH v4 2/6] syscalls/readahead02: abort test if readahead syscall fails Amir Goldstein
2018-12-03 14:27 ` Cyril Hrubis
2018-12-03 14:52 ` Amir Goldstein
2018-11-28 16:46 ` [LTP] [PATCH v4 3/6] syscalls/readahead02: fail test if readahead did not use any cache Amir Goldstein
2018-11-28 16:46 ` [LTP] [PATCH v4 4/6] syscalls/readahead02: Convert to tst_timer helpers Amir Goldstein
2018-11-28 16:46 ` [LTP] [PATCH v4 5/6] syscalls/readahead02: test readahead() on an overlayfs file Amir Goldstein
2018-12-04 14:02 ` Cyril Hrubis
2018-11-28 16:46 ` [LTP] [PATCH v4 6/6] syscalls/readahead02: test readahead using posix_fadvise() Amir Goldstein
2018-12-04 14:10 ` 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=20181203143934.GB4974@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox