linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Cyril Hrubis <chrubis@suse.cz>,
	linux-unionfs@vger.kernel.org, ltp@lists.linux.it,
	Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [LTP] [PATCH 5/5] syscalls/readahead02: fail test if readahead did	not use any cache
Date: Wed, 3 Oct 2018 08:50:34 -0400 (EDT)	[thread overview]
Message-ID: <1897735173.55763513.1538571034299.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180929094432.30197-1-amir73il@gmail.com>


----- Original Message -----
> The heuristic of failing the test only if not saving any io has false
> negatives with overlayfs readahead() bug, but readahead() with overlayfs
> always warns on "using less cache then expected", when actually, it is
> using no cache at all.
> 
> Add another condition to fail the test if readahead did not use any
> cache at all, which always detected the overlayfs bug.

ack, explicit FAIL here looks reasonable

> 
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
> 
> Cyril,
> 
> This is a followup for the overlayfs readahead series.
> With the patches already posted, the test fails sometimes, but
> most of the times it just gets a warning.
> 
> With this additional patch test fails reliably.
> Note that test only fails between these upstream commits:
>   good  b833a3660394 ("ovl: add ovl_fadvise()")
>   bad   5b910bd615ba ("ovl: fix GPF in swapfile_activate...")
> 
> I have a few more minor fixes for the v2 series, but I will hold
> them back until v1 is reviewed.
> 
> Thanks,
> Amir.
> 
>  testcases/kernel/syscalls/readahead/readahead02.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/testcases/kernel/syscalls/readahead/readahead02.c
> b/testcases/kernel/syscalls/readahead/readahead02.c
> index b497fb5db..fbcae1df8 100644
> --- a/testcases/kernel/syscalls/readahead/readahead02.c
> +++ b/testcases/kernel/syscalls/readahead/readahead02.c
> @@ -341,6 +341,8 @@ static void test_readahead(unsigned int n)
>  		 */
>  		if (cached_ra * 1024 > testfile_size / 2)
>  			tst_res(TPASS, "using cache as expected");
> +		else if (!cached_ra)
> +			tst_res(TFAIL, "readahead failed to use any cache");
>  		else
>  			tst_res(TWARN, "using less cache than expected");
>  	} else {
> --
> 2.17.1
> 
> 
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
> 

      reply	other threads:[~2018-10-03 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29  9:44 [PATCH 5/5] syscalls/readahead02: fail test if readahead did not use any cache Amir Goldstein
2018-10-03 12:50 ` Jan Stancek [this message]

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=1897735173.55763513.1538571034299.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=amir73il@gmail.com \
    --cc=chrubis@suse.cz \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=miklos@szeredi.hu \
    /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;
as well as URLs for NNTP newsgroup(s).