From: Caspar Zhang <caspar@casparzhang.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net, Jeffrey Burke <jburke@redhat.com>
Subject: Re: [LTP] [PATCH] move_pages08: E2BIG was removed in 2.6.29
Date: Wed, 09 May 2012 18:31:30 +0800 [thread overview]
Message-ID: <4FAA4782.8040401@casparzhang.com> (raw)
In-Reply-To: <4FAA34CF.6050809@redhat.com>
On 05/09/2012 05:11 PM, Jan Stancek wrote:
> Following commit reworked do_pages_move() to work by page-sized
> chunks and also removed E2BIG:
>
> commit 3140a2273009c01c27d316f35ab76a37e105fdd8
> Author: Brice Goglin <Brice.Goglin@inria.fr>
> Date: Tue Jan 6 14:38:57 2009 -0800
> mm: rework do_pages_move() to work on page_sized chunks
>
> So, move_pages08 makes sense only for kernels < 2.6.29.
>
> Signed-off-by: Jan Stancek <jstancek@redhat.com>
> ---
> .../kernel/syscalls/move_pages/move_pages08.c | 18 ++++++++++++++++--
> 1 files changed, 16 insertions(+), 2 deletions(-)
>
>
>
>
> 0001-move_pages08-E2BIG-was-removed-in-2.6.29.patch
>
>
> diff --git a/testcases/kernel/syscalls/move_pages/move_pages08.c b/testcases/kernel/syscalls/move_pages/move_pages08.c
> index a7ce6e4..f6f01d6 100644
> --- a/testcases/kernel/syscalls/move_pages/move_pages08.c
> +++ b/testcases/kernel/syscalls/move_pages/move_pages08.c
> @@ -46,7 +46,7 @@
> * Initial Version.
> *
> * Restrictions
> - * None
> + * kernel < 2.6.29
> */
>
> #include <sys/mman.h>
> @@ -96,6 +96,20 @@ int main(int argc, char **argv)
> /* reset Tst_count in case we are looping */
> Tst_count = 0;
>
> + /*
> + * commit 3140a2273009c01c27d316f35ab76a37e105fdd8
> + * Author: Brice Goglin <Brice.Goglin@inria.fr>
> + * Date: Tue Jan 6 14:38:57 2009 -0800
> + * mm: rework do_pages_move() to work on page_sized chunks
> + *
> + * reworked do_pages_move() to work by page-sized chunks and removed E2BIG
> + */
> + if ((tst_kvercmp(2, 6, 29)) >= 0) {
> + tst_resm(TCONF, "move_pages: E2BIG was removed in "
> + "commit 3140a2273009c01c27d316f35ab76a37e105fdd8");
> + break;
> + }
> +
Hi Jan,
I think it would be better to put it in setup() function (as we usually
do the kvercmp in setup phase), and just use tst_brkm(TCONF. How do you
think?
Thanks,
Caspar
> ret = alloc_pages_on_node(pages, TEST_PAGES, from_node);
> if (ret == -1)
> continue;
> @@ -151,4 +165,4 @@ void cleanup(void)
> */
> TEST_CLEANUP;
>
> - }
> \ No newline at end of file
> + }
>
------------------------------------------------------------------------------
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
next prev parent reply other threads:[~2012-05-09 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 9:11 [LTP] [PATCH] move_pages08: E2BIG was removed in 2.6.29 Jan Stancek
2012-05-09 9:39 ` Zhouping Liu
2012-05-09 10:31 ` Caspar Zhang [this message]
2012-05-09 10:44 ` Jan Stancek
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=4FAA4782.8040401@casparzhang.com \
--to=caspar@casparzhang.com \
--cc=jburke@redhat.com \
--cc=jstancek@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.