public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Simon Xu <xu.simon@oracle.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH 1/1] madvise03: let the system select an address for shmat()
Date: Fri, 03 Aug 2012 11:46:31 +0800	[thread overview]
Message-ID: <501B4997.8060002@cn.fujitsu.com> (raw)
In-Reply-To: <1343926437-2099-1-git-send-email-xu.simon@oracle.com>

On 08/03/2012 12:53 AM, Simon Xu wrote:
> In certain occasions, 0x22000000 is invalid for shmat() and madvise03 fails:
> 
> madvise03 1 TBROK : shmat error
> madvise03 2 TBROK : Remaining cases broken
> 
> Use `NULL' for shmat() to let the system attach the shared memory segment
> at the first available address.
> 
> Signed-off-by: Simon Xu <xu.simon@oracle.com>
> ---
>  testcases/kernel/syscalls/madvise/madvise03.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/testcases/kernel/syscalls/madvise/madvise03.c b/testcases/kernel/syscalls/madvise/madvise03.c
> index 2e696e8..fd0bd97 100644
> --- a/testcases/kernel/syscalls/madvise/madvise03.c
> +++ b/testcases/kernel/syscalls/madvise/madvise03.c
> @@ -154,13 +154,13 @@ int main(int argc, char *argv[])
>  		if (shmid1 == -1)
>  			tst_brkm(TBROK, cleanup, "shmget failed");
>  
> -		/* Attach shared memory segment to 0x22000000 address */
> -		addr1 = shmat(shmid1, (void *)0x22000000, 0);
> +		/* Attach shared memory segment to an address selected by the system */
> +		addr1 = shmat(shmid1, NULL, 0);
>  		if (addr1 == (void *) -1)
>  			tst_brkm(TBROK, cleanup, "shmat error");
>  
>  		/* (1) Test case for MADV_REMOVE */
> -		TEST(madvise((void *)0x22000000, 4096, MADV_REMOVE));
> +		TEST(madvise((void *)addr1, 4096, MADV_REMOVE));

(void *) is not needed now ?

otherwise, looks OK to me.

Thanks,
Wanlong Gao

>  		check_and_print("MADV_REMOVE");
>  
>  		/* (2) Test case for MADV_DONTFORK */
> 


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2012-08-03  3:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 16:53 [LTP] [PATCH 1/1] madvise03: let the system select an address for shmat() Simon Xu
2012-08-03  3:46 ` Wanlong Gao [this message]
2012-08-03  6:38   ` Jan Stancek
2012-08-03  9:21     ` Simon Xu
2012-08-03  9:24       ` Wanlong Gao

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=501B4997.8060002@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=xu.simon@oracle.com \
    /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