From: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
To: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH 2/2] kernel/mem/lib/mem.c: do the necessary cleanup work
Date: Mon, 28 Apr 2014 19:23:07 +0800 [thread overview]
Message-ID: <535E3A1B.6020502@cn.fujitsu.com> (raw)
In-Reply-To: <535E33C8.3070401@oracle.com>
Hi,
On 04/28/2014 06:56 PM, Stanislav Kholmanskikh wrote:
> Hi!
>
> On 04/28/2014 12:47 PM, Xiaoguang Wang wrote:
>> Oom01 case will modify "/proc/sys/vm/overcommit_memory" to have tests. In most systems,
>> the overcommit_memory's default value is 0. When running oom01, if KSM configuration
>> is not enabled, "tst_brkm(TCONF, NULL, ...)" will be called, in this case, we will forget
>> to execute the restore operation defined in cleanup, and this will impact other test cases
>> in LTP, for example, fork14 in RHEL5 will succeed unexpectedly.
>>
>> Signed-off-by: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
>> ---
>> testcases/kernel/mem/lib/mem.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/testcases/kernel/mem/lib/mem.c b/testcases/kernel/mem/lib/mem.c
>> index f145a2a..69a9014 100644
>> --- a/testcases/kernel/mem/lib/mem.c
>> +++ b/testcases/kernel/mem/lib/mem.c
>> @@ -146,7 +146,7 @@ void testoom(int mempolicy, int lite)
>> oom(MLOCK, lite);
>>
>> if (access(PATH_KSM, F_OK) == -1)
>> - tst_brkm(TCONF, NULL, "KSM configuration is not enabled");
>> + tst_brkm(TCONF, cleanup, "KSM configuration is not enabled");
> In the current situation the OOM test cases will exit with TCONF if no
> KSM is setup on the system.
>
> But is KSM the absolute requirement for the test cases?
According to my understanding about oom01, this is not a mandatory requirement :-)
>
> And could we execute the KSM part of testoom() only if KSM is enabled?
Yeah, sound reasonable, thanks. I will make a new version soon.
Regards,
Xiaoguang Wang
>
> Thanks.
>
>> tst_resm(TINFO, "start OOM testing for KSM pages.");
>> oom(KSM, lite);
>>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos. Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-04-28 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 8:47 [LTP] [PATCH 1/2] kernel/mem/lib/mem.c: fix compilation warnings Xiaoguang Wang
2014-04-28 8:47 ` [LTP] [PATCH 2/2] kernel/mem/lib/mem.c: do the necessary cleanup work Xiaoguang Wang
2014-04-28 10:56 ` Stanislav Kholmanskikh
2014-04-28 11:23 ` Xiaoguang Wang [this message]
2014-04-28 10:29 ` [LTP] [PATCH 1/2] kernel/mem/lib/mem.c: fix compilation warnings Stanislav Kholmanskikh
2014-05-05 6:13 ` 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=535E3A1B.6020502@cn.fujitsu.com \
--to=wangxg.fnst@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=stanislav.kholmanskikh@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