From: Alex Shi <alex.shi@linux.alibaba.com>
To: Qian Cai <cai@lca.pw>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
aarcange@redhat.com, daniel.m.jordan@oracle.com,
hannes@cmpxchg.org, hughd@google.com, khlebnikov@yandex-team.ru,
kirill@shutemov.name, kravetz@us.ibm.com, mhocko@kernel.org,
mm-commits@vger.kernel.org, tj@kernel.org,
vdavydov.dev@gmail.com, willy@infradead.org,
yang.shi@linux.alibaba.com
Subject: Re: [failures] mm-vmscan-remove-unnecessary-lruvec-adding.patch removed from -mm tree
Date: Sat, 7 Mar 2020 11:26:47 +0800 [thread overview]
Message-ID: <7149d2fb-2ff2-d251-2ed1-b4e6d81748ee@linux.alibaba.com> (raw)
In-Reply-To: <792CE873-A64B-4FA6-A258-A8B6B951E698@lca.pw>
在 2020/3/7 上午10:27, Qian Cai 写道:
>> Compare to this patch's change, the 'c8cba0cc2a80 mm/thp: narrow lru locking' is more
>> likely bad. Maybe it's due to lru unlock was moved before ClearPageCompound() from
>> before remap_page(head); guess this unlock should be move after ClearPageCompound or
>> move back to origin place.
> I can only confirmed that after reverted those 6 patches, I am no long be able to reproduce it.
>
Hi Qian,
Thanks for response!
Could you like just try to revert the patch: 'mm/thp: narrow lru locking'? or would you like to
share me info of your tests and let me reproduce it? like kernel config, system ENV, machine type.
I had run hundreds cycle of oom01, but akpm kernel(f2cbd107a99b) still survived.
I got my ltp mm testing results, it run total 75 cases, failed 2, skip 9 and others are success
and kernel works well after test on yesterday's akmp head: f2cbd107a99b.
Many Thanks for help!
Alex
=====
Test Start Time: Fri Mar 6 20:49:59 2020
-----------------------------------------
Testcase Result Exit Value
-------- ------ ----------
mm01 PASS 0
mm02 PASS 0
mtest01 PASS 0
mtest01w PASS 0
mtest05 PASS 0
mtest06 PASS 0
mtest06_2 PASS 0
mtest06_3 PASS 0
mem01 PASS 0
mem02 PASS 0
mem03 PASS 0
page01 PASS 0
page02 PASS 0
data_space PASS 0
stack_space PASS 0
shmt02 PASS 0
shmt03 PASS 0
shmt04 PASS 0
shmt05 PASS 0
shmt06 PASS 0
shmt07 PASS 0
shmt08 PASS 0
shmt09 PASS 0
shmt10 PASS 0
shm_test01 PASS 0
mallocstress01 PASS 0
mmapstress01 PASS 0
mmapstress02 PASS 0
mmapstress03 PASS 0
mmapstress04 PASS 0
mmapstress05 PASS 0
mmapstress06 PASS 0
mmapstress07 PASS 0
mmapstress08 PASS 0
mmapstress09 PASS 0
mmapstress10 PASS 0
mmap10 PASS 0
mmap10_1 PASS 0
mmap10_2 PASS 0
mmap10_3 PASS 0
mmap10_4 PASS 0
ksm01 FAIL 2
ksm01_1 FAIL 1
ksm02 CONF 32
ksm02_1 CONF 32
ksm03 PASS 0
ksm03_1 PASS 0
ksm04 CONF 32
ksm04_1 CONF 32
ksm05 PASS 0
ksm06 CONF 32
ksm06_1 CONF 32
ksm06_2 CONF 32
oom01 PASS 0
oom02 CONF 32
oom03 PASS 0
oom04 PASS 0
oom05 PASS 0
swapping01 PASS 0
thp01 PASS 0
thp02 PASS 0
thp03 PASS 0
vma01 PASS 0
vma02 PASS 0
vma03 CONF 32
vma04 PASS 0
vma05 PASS 0
overcommit_memory01 PASS 0
overcommit_memory02 PASS 0
overcommit_memory03 PASS 0
overcommit_memory04 PASS 0
overcommit_memory05 PASS 0
overcommit_memory06 PASS 0
max_map_count PASS 0
min_free_kbytes PASS 0
-----------------------------------------------
Total Tests: 75
Total Skipped Tests: 9
Total Failures: 2
Kernel Version: 5.6.0-rc4-06724-gf2cbd107a99b
Machine Architecture: x86_64
Hostname: alexshi-test
next prev parent reply other threads:[~2020-03-07 3:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200306025041.rERhvnYmB%akpm@linux-foundation.org>
2020-03-06 3:32 ` [failures] mm-vmscan-remove-unnecessary-lruvec-adding.patch removed from -mm tree Qian Cai
2020-03-06 3:38 ` Matthew Wilcox
2020-03-06 3:50 ` Qian Cai
2020-03-06 4:17 ` Hugh Dickins
2020-03-06 4:42 ` Alex Shi
2020-03-06 4:46 ` Qian Cai
2020-03-06 13:30 ` Alex Shi
2020-03-06 14:54 ` Johannes Weiner
2020-03-06 9:04 ` Alex Shi
2020-03-06 11:58 ` Alex Shi
2020-03-07 2:27 ` Qian Cai
2020-03-07 3:26 ` Alex Shi [this message]
2020-03-07 3:31 ` Qian Cai
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=7149d2fb-2ff2-d251-2ed1-b4e6d81748ee@linux.alibaba.com \
--to=alex.shi@linux.alibaba.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=daniel.m.jordan@oracle.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=khlebnikov@yandex-team.ru \
--cc=kirill@shutemov.name \
--cc=kravetz@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=tj@kernel.org \
--cc=vdavydov.dev@gmail.com \
--cc=willy@infradead.org \
--cc=yang.shi@linux.alibaba.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