public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Caspar Zhang <czhang@redhat.com>
To: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH v5] thp testcase come from CVE reproducer
Date: Fri, 06 May 2011 11:46:13 +0800	[thread overview]
Message-ID: <4DC36F05.6080704@redhat.com> (raw)
In-Reply-To: <5da8d206a0df7808faed5039ade03c433af02abc.1304148727.git.czhang@redhat.com>

On 04/30/2011 04:46 PM, Caspar Zhang wrote:
> 
> This is a reproducer of CVE-2011-0999, which fixed by mainline commit
> a7d6e4ecdb7648478ddec76d30d87d03d6e22b31:
> 
> "Transparent hugepages can only be created if rmap is fully functional.
> So we must prevent hugepages to be created while
> is_vma_temporary_stack() is true."
> 
> When running in a loop, it can trigger panic like this, if kernel
> unpatched:
> 
> kernel BUG at mm/huge_memory.c:1260!
> invalid opcode: 0000 [#1] SMP
> last sysfs file: /sys/devices/system/cpu/cpu23/cache/index2/shared_cpu_map
> ....
> 
> So I recommend to run it as 'thp01 -I xxx'.
> 
> v5: not using hard depend on /bin/true, use execvp() and "true" instead.
> 
> Signed-off-by: Pingtian Han <phan@redhat.com>
> Signed-off-by: Caspar Zhang <czhang@redhat.com>
> ---
>  runtest/mm                        |    2 +
>  testcases/kernel/mem/thp/Makefile |   23 +++++++
>  testcases/kernel/mem/thp/thp01.c  |  124 +++++++++++++++++++++++++++++++++++++
>  3 files changed, 149 insertions(+), 0 deletions(-)
>  create mode 100644 testcases/kernel/mem/thp/Makefile
>  create mode 100644 testcases/kernel/mem/thp/thp01.c
> 

Hi all, I've modified the patch as suggested and tested it. Any comments
on this new case?

Thanks,
Caspar

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2011-05-06  3:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 10:36 [LTP] [PATCH] thp testcase come from CVE reproducer Han Pingtian
2011-03-04 10:38 ` Garrett Cooper
2011-03-07  7:29   ` Han Pingtian
2011-03-11  4:54     ` Han Pingtian
2011-04-06 19:19     ` Cyril Hrubis
     [not found]       ` <BANLkTik=ZwxHTEgF_E9UeC1Tutx-MRnMkw@mail.gmail.com>
2011-04-07 19:41         ` Cyril Hrubis
2011-04-07  6:57 ` Garrett Cooper
2011-04-09  3:23   ` Han Pingtian
2011-04-09  6:12     ` Garrett Cooper
2011-04-27  3:40       ` [LTP] [PATCH v3] " Caspar Zhang
2011-04-28 15:49         ` Cyril Hrubis
2011-04-30  2:56           ` [LTP] [PATCH v4] " Caspar Zhang
2011-04-30  3:05             ` Mike Frysinger
2011-04-30  8:46               ` [LTP] [PATCH v5] " Caspar Zhang
2011-05-06  3:46                 ` Caspar Zhang [this message]
2011-05-06 13:41                 ` Cyril Hrubis
2011-05-30 14:46                   ` [LTP] [PATCH v6] mm: " Caspar Zhang
2011-05-31 15:32                     ` 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=4DC36F05.6080704@redhat.com \
    --to=czhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox