From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux- stable <stable@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
William Kucharski <william.kucharski@oracle.com>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Michal Hocko <mhocko@kernel.org>,
Will Deacon <will.deacon@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
lkft-triage@lists.linaro.org,
Mike Kravetz <mike.kravetz@oracle.com>,
LTP List <ltp@lists.linux.it>
Subject: Re: mm/mremap.c : WARNING: at mm/mremap.c:211 move_page_tables+0x5b0/0x5d0
Date: Sat, 4 Apr 2020 19:06:31 +0300 [thread overview]
Message-ID: <20200404160631.7eny3swsqn665m2p@box> (raw)
In-Reply-To: <CA+G9fYsnD0vkCpSH98Lpsi6nxXBS+JYbSPhTnNE16CrQ4s4QhQ@mail.gmail.com>
On Sat, Apr 04, 2020 at 08:10:42PM +0530, Naresh Kamboju wrote:
> On Fri, 3 Apr 2020 at 19:02, Kirill A. Shutemov <kirill@shutemov.name> wrote:
> >
> > On Fri, Apr 03, 2020 at 12:56:57AM +0530, Naresh Kamboju wrote:
> > > [ 734.876355] old_addr: 0xbfe00000, new_addr: 0xbfc00000, old_end: 0xc0000000
> >
> > The ranges are overlapping. We don't expect it. mremap(2) never does this.
> >
> > shift_arg_pages() only moves range downwards. It should be safe.
> >
> > Could you try this:
>
> Applied the patch and tested and still getting kernel warning.
> CONFIG_HIGHMEM64G=y is still enabled.
>
> [ 790.041040] ------------[ cut here ]------------
> [ 790.045664] WARNING: CPU: 3 PID: 3195 at mm/mremap.c:212
> move_page_tables+0x7a7/0x840
Are you sure the patch is applied? The line number in the warning supposed
to change.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2020-04-04 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 11:19 Naresh Kamboju
2020-04-02 13:38 ` Kirill A. Shutemov
2020-04-02 19:26 ` Naresh Kamboju
2020-04-03 13:32 ` Kirill A. Shutemov
2020-04-04 14:40 ` Naresh Kamboju
2020-04-04 16:06 ` Kirill A. Shutemov [this message]
2020-04-06 8:23 ` Naresh Kamboju
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=20200404160631.7eny3swsqn665m2p@box \
--to=kirill@shutemov.name \
--cc=Julia.Lawall@lip6.fr \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=naresh.kamboju@linaro.org \
--cc=stable@vger.kernel.org \
--cc=will.deacon@arm.com \
--cc=william.kucharski@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