From: Dmitry Osipenko <digetx@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wei Yang <richardw.yang@linux.intel.com>,
dan.j.williams@intel.com, aneesh.kumar@linux.ibm.com,
kirill@shutemov.name, yang.shi@linux.alibaba.com,
thellstrom@vmware.com, Thierry Reding <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: Re: [PATCH 3/5] mm/mremap: use pmd_addr_end to calculate next in move_page_tables()
Date: Wed, 29 Jan 2020 20:18:56 +0300 [thread overview]
Message-ID: <b5eb4766-38ba-0153-2844-cc303fe0dc07@gmail.com> (raw)
In-Reply-To: <20200126185951.c9246349befcccce210a4ab8@linux-foundation.org>
27.01.2020 05:59, Andrew Morton пишет:
> On Sun, 26 Jan 2020 17:47:57 +0300 Dmitry Osipenko <digetx@gmail.com> wrote:
...
>> Hello Wei,
>>
>> Starting with next-20200122, I'm seeing the following in KMSG on NVIDIA
>> Tegra (ARM32):
>>
>> BUG: Bad rss-counter state mm:(ptrval) type:MM_ANONPAGES val:190
>>
>> and eventually kernel hangs.
>>
>> Git's bisection points to this patch and reverting it helps. Please fix,
>> thanks in advance.
>
> Thanks. I had these tagged for 5.7-rc1 anyway, so I'll drop all five
> patches.
>
Hello Andrew,
FYI, I'm still seeing the offending patches in the today's next-20200129.
next prev parent reply other threads:[~2020-01-29 17:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 23:22 [PATCH 0/5] mm/mremap.c: cleanup move_page_tables() a little Wei Yang
2020-01-17 23:22 ` [PATCH 1/5] mm/mremap: format the check in move_normal_pmd() same as move_huge_pmd() Wei Yang
2020-01-17 23:22 ` [PATCH 2/5] mm/mremap: it is sure to have enough space when extent meets requirement Wei Yang
2020-01-17 23:22 ` [PATCH 3/5] mm/mremap: use pmd_addr_end to calculate next in move_page_tables() Wei Yang
2020-01-26 14:47 ` Dmitry Osipenko
2020-01-27 2:59 ` Andrew Morton
2020-01-29 17:18 ` Dmitry Osipenko [this message]
2020-01-29 23:59 ` Andrew Morton
2020-01-30 0:28 ` Stephen Rothwell
2020-01-28 0:43 ` Wei Yang
2020-01-28 15:59 ` Dmitry Osipenko
2020-01-28 23:29 ` Wei Yang
2020-01-28 23:35 ` Dmitry Osipenko
2020-01-29 0:28 ` Wei Yang
2020-01-29 18:56 ` Dmitry Osipenko
2020-01-29 9:47 ` Russell King - ARM Linux admin
2020-01-29 14:21 ` Dmitry Osipenko
2020-01-29 21:57 ` Wei Yang
2020-01-29 23:24 ` Russell King - ARM Linux admin
2020-01-30 1:30 ` Wei Yang
2020-01-30 14:15 ` Russell King - ARM Linux admin
2020-01-30 21:57 ` Wei Yang
2020-01-17 23:22 ` [PATCH 4/5] mm/mremap: calculate extent in one place Wei Yang
2020-01-17 23:22 ` [PATCH 5/5] mm/mremap: start addresses are properly aligned Wei Yang
2020-01-19 0:07 ` [PATCH 0/5] mm/mremap.c: cleanup move_page_tables() a little Andrew Morton
2020-01-19 2:11 ` Wei Yang
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=b5eb4766-38ba-0153-2844-cc303fe0dc07@gmail.com \
--to=digetx@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=jonathanh@nvidia.com \
--cc=kirill@shutemov.name \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=richardw.yang@linux.intel.com \
--cc=thellstrom@vmware.com \
--cc=thierry.reding@gmail.com \
--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).