From: Yanteng Si <si.yanteng@linux.dev>
To: Tianyang Zhang <zhangtianyang@loongson.cn>,
chenhuacai@kernel.org, kernel@xen0n.name,
zhanghongchen@loongson.cn, wangming01@loongson.cn,
peterx@redhat.com
Cc: loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Loongarch:Fixed up panic cause by a NULL-pmd
Date: Tue, 27 May 2025 13:47:17 +0800 [thread overview]
Message-ID: <1876bf9a-a77d-40a5-bedd-643df939bfbf@linux.dev> (raw)
In-Reply-To: <20250526065512.13215-1-zhangtianyang@loongson.cn>
在 5/26/25 2:55 PM, Tianyang Zhang 写道:
> From: zhangtianyang <zhangtianyang@loongson.cn>
>
> Fixes: bd51834d1cf6 ("LoongArch: Return NULL from huge_pte_offset() for invalid PMD")
> ERROR INFO:
>
> CPU 25 Unable to handle kernel paging request at virtual address 0x0
> ...
> Call Trace:
> [<900000000023c30c>] huge_pte_offset+0x3c/0x58
> [<900000000057fd4c>] hugetlb_follow_page_mask+0x74/0x438
> [<900000000051fee8>] __get_user_pages+0xe0/0x4c8
> [<9000000000522414>] faultin_page_range+0x84/0x380
> [<9000000000564e8c>] madvise_vma_behavior+0x534/0xa48
> [<900000000056689c>] do_madvise+0x1bc/0x3e8
> [<9000000000566df4>] sys_madvise+0x24/0x38
> [<90000000015b9e88>] do_syscall+0x78/0x98
> [<9000000000221f18>] handle_syscall+0xb8/0x158
>
> In some cases, pmd may be NULL and rely on NULL as the return value
> for processing, so it is necessary to determine this situation here
Your description is a bit vague. Could you please specify
on which machines and in what scenarios this bug can be
reproduced? I believe such information should be included
in the commit message.
Thanks,
Yanteng
next prev parent reply other threads:[~2025-05-27 5:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 6:55 [PATCH] Loongarch:Fixed up panic cause by a NULL-pmd Tianyang Zhang
2025-05-27 5:47 ` Yanteng Si [this message]
2025-06-05 1:16 ` Tianyang Zhang
2025-06-05 1:35 ` Huacai Chen
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=1876bf9a-a77d-40a5-bedd-643df939bfbf@linux.dev \
--to=si.yanteng@linux.dev \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=peterx@redhat.com \
--cc=wangming01@loongson.cn \
--cc=zhanghongchen@loongson.cn \
--cc=zhangtianyang@loongson.cn \
/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).