public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Caspar Zhang <caspar@casparzhang.com>
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH 3/3] syscalls/madvise02: fix madvise case due to kernel change
Date: Thu, 07 Mar 2013 16:17:52 +0800	[thread overview]
Message-ID: <51384D30.1040003@cn.fujitsu.com> (raw)
In-Reply-To: <0da7f15cb693ea31f3f5cb1512713ae0562b4f17.1362641893.git.caspar@casparzhang.com>

On 03/07/2013 03:38 PM, Caspar Zhang wrote:
> since kernel commit 1998cc0 (after kernel-3.8 released),
> madvise(MADV_WILLNEED) to anonymous memory doesn't return -EBADF now, as
> now we support swap prefetch. Thus the 5th testcase in madvise02 will
> not pass. This patch fixes this by adding a tst_kvercmp() condition, and
> will give a pass if kernel is >=3.9 (including the RCs).
> 
> Signed-off-by: Caspar Zhang <caspar@casparzhang.com>
> ---
>  testcases/kernel/syscalls/madvise/madvise02.c | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)
> 
> 
> 0003-syscalls-madvise02-fix-madvise-case-due-to-kernel-ch.patch
> 
> 
> diff --git a/testcases/kernel/syscalls/madvise/madvise02.c b/testcases/kernel/syscalls/madvise/madvise02.c
> index 87d26c3..f68fb0b 100644
> --- a/testcases/kernel/syscalls/madvise/madvise02.c
> +++ b/testcases/kernel/syscalls/madvise/madvise02.c
> @@ -187,7 +187,15 @@ int main(int argc, char *argv[])
>  
>  		TEST(madvise
>  		     (tmp_memory_allocated, 5 * pagesize, MADV_WILLNEED));
> -		check_and_print(EBADF);
> +		if (tst_kvercmp(3, 9, 0) < 0)
> +			check_and_print(EBADF);
> +		/* in kernel commit 1998cc0, madvise(MADV_WILLNEED) to anon
> +		 * mem doesn't return -EBADF now, as now we suuport swap

Please s/suuport/support/ when you push this patch.

Reviewed-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>

> +		 * prefretch.
> +		 */
> +		else
> +			tst_resm(TPASS, "madvise succeeded as expected, see "
> +					"kernel commit 1998cc0 for details.");
>  		free((void *)ptr_memory_allocated);
>  
>  		close(fd);
> 
> 


------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2013-03-07  8:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07  7:38 [LTP] [PATCH 1/3] s/Tst_count/tst_count/ to avoid CamelCase Caspar Zhang
2013-03-07  7:38 ` [LTP] [PATCH 2/3] syscalls/madvise: code cleanup Caspar Zhang
2013-03-07  8:27   ` Wanlong Gao
2013-03-07  7:38 ` [LTP] [PATCH 3/3] syscalls/madvise02: fix madvise case due to kernel change Caspar Zhang
2013-03-07  8:17   ` Wanlong Gao [this message]
2013-03-07  8:20     ` Caspar Zhang
2013-03-07  8:24   ` Zhouping Liu
2013-03-07  8:33 ` [LTP] [PATCH 1/3] s/Tst_count/tst_count/ to avoid CamelCase Wanlong Gao
2013-03-07  8:32   ` Caspar Zhang

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=51384D30.1040003@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=caspar@casparzhang.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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