From: David Hildenbrand <david@redhat.com>
To: Hongchen Zhang <zhanghongchen@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Andrew Morton <akpm@linux-foundation.org>,
"Mike Rapoport IBM)" <rppt@kernel.org>,
Feiyang Chen <chenfeiyang@loongson.cn>,
Qi Zheng <zhengqi.arch@bytedance.com>,
"Matthew Wilcox Oracle)" <willy@infradead.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH] LoongArch: add p?d_leaf() definitions
Date: Wed, 6 Sep 2023 10:08:28 +0200 [thread overview]
Message-ID: <a371b120-5536-1054-7f09-957b427e46ff@redhat.com> (raw)
In-Reply-To: <4a06f415-281f-b76f-ed03-211b07ccd6a4@loongson.cn>
On 06.09.23 10:06, Hongchen Zhang wrote:
> Hi David,
>
> On 2023/9/6 pm 3:42, David Hildenbrand wrote:
>> On 05.09.23 08:49, Hongchen Zhang wrote:
>>> When I do LTP test, LTP test case ksm06 caused panic at
>>> break_ksm_pmd_entry
>>> -> pmd_leaf (Huge page table but False)
>>> -> pte_present (panic)
>>>
>>
>> Probably there are other problematic bits without that can trigger that?
>> I suspect walk_page_range*() callers might be affected,
> I rechecked the code and found that other architectures that support
> THP have defined pmd_leaf.
> So there is not problem on other architectures.
I meant other walk_page_range*() callers on loongarch might similarly be
affected. IOW, KSM might not be the only bit being able to trigger such
panics on loongarch.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-09-06 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 6:49 Hongchen Zhang
2023-09-06 7:42 ` David Hildenbrand
2023-09-06 8:06 ` Hongchen Zhang
2023-09-06 8:08 ` David Hildenbrand [this message]
2023-09-06 8:22 ` Hongchen Zhang
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=a371b120-5536-1054-7f09-957b427e46ff@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=chenfeiyang@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=rppt@kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=zhanghongchen@loongson.cn \
--cc=zhengqi.arch@bytedance.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
all inboxes | Powered by JetHome®