From: yang.shi@linaro.org (Shi, Yang)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] set_pte_at: racy dirty state clearing warning
Date: Wed, 27 Apr 2016 09:50:33 -0700 [thread overview]
Message-ID: <50501020-db93-cb6c-c2d9-b59efc05c30d@linaro.org> (raw)
In-Reply-To: <20160421084946.GA23774@e104818-lin.cambridge.arm.com>
On 4/21/2016 1:49 AM, Catalin Marinas wrote:
> On Wed, Apr 20, 2016 at 04:01:39PM -0700, Shi, Yang wrote:
>> When I enable memory comact via
>>
>> # echo 1 > /proc/sys/vm/compact_memory
>>
>> I got the below WARNING:
>>
>> set_pte_at: racy dirty state clearing: 0x0068000099371bd3 ->
>> 0x0068000099371fd3
>> ------------[ cut here ]------------
>> WARNING: CPU: 5 PID: 294 at ./arch/arm64/include/asm/pgtable.h:227
>> ptep_set_access_flags+0x138/0x1b8
>> Modules linked in:
>
> Do you have this patch applied:
>
> http://article.gmane.org/gmane.linux.ports.arm.kernel/492239
>
> It's also queued into -next as commit 66dbd6e61a52.
No, but I just applied it, it works.
Thanks,
Yang
>
>> My kernel has ARM64_HW_AFDBM enabled, but LS2085 is not ARMv8.1.
>>
>> The code shows it just check if ARM64_HW_AFDBM is enabled or not, but
>> doesn't check if the CPU really has such capability.
>>
>> So, it might be better to have the capability checked runtime?
>
> The warnings are there to spot any incorrect uses of the pte accessors
> even before you run on AF/DBM-capable hardware.
>
prev parent reply other threads:[~2016-04-27 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 23:01 [BUG] set_pte_at: racy dirty state clearing warning Shi, Yang
2016-04-21 8:49 ` Catalin Marinas
2016-04-27 16:50 ` Shi, Yang [this message]
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=50501020-db93-cb6c-c2d9-b59efc05c30d@linaro.org \
--to=yang.shi@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).