From: Jia He <hejianet@gmail.com>
To: Suzuki K Poulose <Suzuki.Poulose@arm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Minchan Kim <minchan@kernel.org>,
Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>,
Arvind Yadav <arvind.yadav.cs@gmail.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
jia.he@hxt-semitech.com, Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH v2] mm/ksm: ignore STABLE_FLAG of rmap_item->address in rmap_walk_ksm
Date: Thu, 24 May 2018 16:50:16 +0800 [thread overview]
Message-ID: <198fe48c-0d26-7dd1-89dc-415bd3c7ab41@gmail.com> (raw)
In-Reply-To: <6c417ab1-a808-72ea-9618-3d76ec203684@arm.com>
Hi Suzuki
On 5/24/2018 4:44 PM, Suzuki K Poulose Wrote:
> On 14/05/18 10:45, Suzuki K Poulose wrote:
>> On 10/05/18 00:31, Andrew Morton wrote:
>>> On Fri,A 4 May 2018 11:11:46 +0800 Jia He <hejianet@gmail.com> wrote:
>>>
>>>> In our armv8a server(QDF2400), I noticed lots of WARN_ON caused by PAGE_SIZE
>>>> unaligned for rmap_item->address under memory pressure tests(start 20 guests
>>>> and run memhog in the host).
>>>>
>>>> ...
>>>>
>>>> In rmap_walk_ksm, the rmap_item->address might still have the STABLE_FLAG,
>>>> then the start and end in handle_hva_to_gpa might not be PAGE_SIZE aligned.
>>>> Thus it will cause exceptions in handle_hva_to_gpa on arm64.
>>>>
>>>> This patch fixes it by ignoring(not removing) the low bits of address when
>>>> doing rmap_walk_ksm.
>>>>
>>>> Signed-off-by: jia.he@hxt-semitech.com
>>>
>>> I assumed you wanted this patch to be committed as
>>> From:jia.he@hxt-semitech.com rather than From:hejianet@gmail.com, so I
>>> made that change.A Please let me know if this was inappropriate.
>>>
>>> You can do this yourself by adding an explicit From: line to the very
>>> start of the patch's email text.
>>>
>>> Also, a storm of WARN_ONs is pretty poor behaviour.A Is that the only
>>> misbehaviour which this bug causes?A Do you think the fix should be
>>> backported into earlier kernels?
>>>
>
>
> Jia, Andrew,
>
> What is the status of this patch ?
>
> Suzuki
I thought the patch is merged into mmotm tree.
http://www.ozlabs.org/~akpm/mmotm/series
But I don't know what is the next step.
Cheers,
Jia
next prev parent reply other threads:[~2018-05-24 8:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 8:34 [PATCH] mm/ksm: ignore STABLE_FLAG of rmap_item->address in rmap_walk_ksm Jia He
2018-05-03 10:44 ` Claudio Imbrenda
2018-05-03 13:23 ` Jia He
2018-05-04 3:11 ` [PATCH v2] " Jia He
2018-05-04 5:56 ` Jia He
2018-05-09 23:31 ` Andrew Morton
2018-05-10 1:26 ` Jia He
2018-05-14 9:09 ` Suzuki K Poulose
2018-05-14 9:45 ` Suzuki K Poulose
2018-05-24 8:44 ` Suzuki K Poulose
2018-05-24 8:50 ` Jia He [this message]
2018-05-24 9:01 ` Suzuki K Poulose
2018-05-24 9:36 ` Jia He
2018-05-24 20:38 ` Andrew Morton
2018-06-07 22:13 ` Andrew Morton
2018-06-07 23:38 ` Andrea Arcangeli
2018-06-08 1:32 ` Jia He
2018-06-08 1:23 ` Jia He
2018-06-08 11:08 ` Suzuki K Poulose
2018-05-03 13:41 ` [PATCH] " Michal Hocko
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=198fe48c-0d26-7dd1-89dc-415bd3c7ab41@gmail.com \
--to=hejianet@gmail.com \
--cc=Suzuki.Poulose@arm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arvind.yadav.cs@gmail.com \
--cc=hughd@google.com \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=jia.he@hxt-semitech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=rppt@linux.vnet.ibm.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).