From: Alex Shi <alex.shi@linux.alibaba.com>
To: Qian Cai <cai@lca.pw>, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: 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: Fri, 6 Mar 2020 19:58:19 +0800 [thread overview]
Message-ID: <f37b9b6b-730b-09b0-dd6b-5acba53e71e6@linux.alibaba.com> (raw)
In-Reply-To: <b123f1d8-eab0-4689-9400-ba1f853728b7@linux.alibaba.com>
在 2020/3/6 下午5:04, Alex Shi 写道:
>
>
> 在 2020/3/6 上午11:32, Qian Cai 写道:
>>
>>> On Mar 5, 2020, at 9:50 PM, akpm@linux-foundation.org wrote:
>>>
>>>
>>> The patch titled
>>> Subject: mm/vmscan: remove unnecessary lruvec adding
>>> has been removed from the -mm tree. Its filename was
>>> mm-vmscan-remove-unnecessary-lruvec-adding.patch
>>>
>>> This patch was dropped because it had testing failures
>> Andrew, do you have more information about this failure? I hit a bug
>> here under memory pressure and am wondering if this is related
>> which might save me some time digging…
>>
>> [ 4389.727184][ T6600] mem_cgroup_update_lru_size(00000000bb31aaed, 0, -7): lru_size -1
>
> This bug seems failed due to a update_lru_size() missing or misplace, but
> what's I changed on this patch seems unlike to cause this bug.
>
> Anyway, Qian, could you do me a favor to remove this patch and try again?
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.
But I still can not reproduce this bug. Awkward!
Alex
---
line 2605 mm/huge_memory.c:
spin_unlock_irqrestore(&pgdat->lru_lock, flags);
ClearPageCompound(head);
split_page_owner(head, HPAGE_PMD_ORDER);
/* See comment in __split_huge_page_tail() */
if (PageAnon(head)) {
/* Additional pin to swap cache */
if (PageSwapCache(head)) {
page_ref_add(head, 2);
xa_unlock(&swap_cache->i_pages);
} else {
page_ref_inc(head);
}
} else {
/* Additional pin to page cache */
page_ref_add(head, 2);
xa_unlock(&head->mapping->i_pages);
}
remap_page(head);
next prev parent reply other threads:[~2020-03-06 11:58 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 [this message]
2020-03-07 2:27 ` Qian Cai
2020-03-07 3:26 ` Alex Shi
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=f37b9b6b-730b-09b0-dd6b-5acba53e71e6@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;
as well as URLs for NNTP newsgroup(s).