mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Arcangeli <aarcange@redhat.com>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Hugh Dickins <hughd@google.com>,
	Petr Holasek <pholasek@redhat.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [lkp] [ksm] 40e318e509: ltp.ksm01.fail
Date: Mon, 25 Jan 2016 15:54:26 +0100	[thread overview]
Message-ID: <20160125145426.GB12228@redhat.com> (raw)
In-Reply-To: <87io2ibbrh.fsf@yhuang-dev.intel.com>

Hello,

On Mon, Jan 25, 2016 at 11:04:18AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 40e318e509d2c9f3cdb00ef32d2c14b9868af16b ("ksm: introduce ksm_max_page_sharing per page deduplication limit")
> 
> We found LKP KSM test case failed for your patch.
> 
> =========================================================================================
> compiler/kconfig/rootfs/tbox_group/test/testcase:
>   gcc-5/x86_64-nfsroot/debian-x86_64-2015-02-07.cgz/vm-lkp-wsx03-4G/mm_functional_positive/otc_kernel_qa-ts_ltp_ddt
> 
> commit: 
>   77505a33e539477f1fbe5e6136df5b265f39cccf
>   40e318e509d2c9f3cdb00ef32d2c14b9868af16b
> 
> 77505a33e539477f 40e318e509d2c9f3cdb00ef32d 
> ---------------- -------------------------- 
>        fail:runs  %reproduction    fail:runs
>            |             |             |    
>            :4          100%           4:4     otc_kernel_qa-ts_ltp_ddt.ksm01.fail
>            :4          100%           4:4     otc_kernel_qa-ts_ltp_ddt.ksm01_1.fail

In this case it's one rare case of false positive. The change in the
merging levels is a "feature" not a "bug".

LTP validation math on ksm sysfs levels shall be updated to account
for the runtime value of /sys/kernel/mm/ksm/max_page_sharing which in
turn affects pages_sharing/pages_shared. In fact you could add
validation for the new fields like stable_node_dups and
stable_node_chains on top of the existing verifications on pages_shar*.

For now you should re-run the test after:

    echo 2 >/sys/kernel/mm/ksm/run
    echo 10000000 > /sys/kernel/mm/ksm/max_page_sharing
    echo 1 >/sys/kernel/mm/ksm/run

And then LTP will pass as usual.

Thanks for the greatly valuable regression testing work,
Andrea

      reply	other threads:[~2016-01-25 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  3:04 kernel test robot
2016-01-25 14:54 ` Andrea Arcangeli [this message]

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=20160125145426.GB12228@redhat.com \
    --to=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=dave@stgolabs.net \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=pholasek@redhat.com \
    --cc=sfr@canb.auug.org.au \
    --cc=ying.huang@linux.intel.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

Powered by JetHome