From: Sean Christopherson <seanjc@google.com>
To: kernel test robot <yujie.liu@intel.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
kasan-dev@googlegroups.com, Han Ning <ning.han@intel.com>
Subject: Re: [tip:x86/mm] [x86/kasan] 9fd429c280: BUG:unable_to_handle_page_fault_for_address
Date: Tue, 15 Nov 2022 00:28:22 +0000 [thread overview]
Message-ID: <Y3LdJni8+ye/soOV@google.com> (raw)
In-Reply-To: <202211121255.f840971-yujie.liu@intel.com>
On Sat, Nov 12, 2022, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed BUG:unable_to_handle_page_fault_for_address due to commit (built with gcc-11):
>
> commit: 9fd429c28073fa40f5465cd6e4769a0af80bf398 ("x86/kasan: Map shadow for percpu pages on demand")
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git x86/mm
>
> [test failed on linux-next/master f8f60f322f0640c8edda2942ca5f84b7a27c417a]
>
> on test machine: 128 threads 2 sockets Intel(R) Xeon(R) Platinum 8358 CPU @ 2.60GHz (Ice Lake) with 128G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> [ 158.064712][ T8416] BUG: unable to handle page fault for address: fffffbc00012de04
> [ 158.074534][ T8416] #PF: supervisor read access in kernel mode
> [ 158.074537][ T8416] #PF: error_code(0x0000) - not-present page
> [ 158.095763][ T8416] PGD 207e210067 P4D 1fef217067 PUD 1fef216067 PMD 103344b067 PTE 0
> [ 158.095770][ T8416] Oops: 0000 [#1] SMP KASAN NOPTI
> [ 158.095773][ T8416] CPU: 34 PID: 8416 Comm: umip_test_basic Not tainted 6.1.0-rc2-00001-g9fd429c28073 #1
> [ 158.107429][ T8416] RIP: 0010:get_desc (arch/x86/lib/insn-eval.c:660)
> [ 158.107465][ T8416] insn_get_seg_base (arch/x86/lib/insn-eval.c:725)
> [ 158.117492][ T8416] insn_fetch_from_user (arch/x86/lib/insn-eval.c:1476 arch/x86/lib/insn-eval.c:1505)
> [ 158.117496][ T8416] fixup_umip_exception (arch/x86/kernel/umip.c:353)
> [ 158.187382][ T8416] exc_general_protection (arch/x86/kernel/traps.c:733 arch/x86/kernel/traps.c:721)
> [ 158.187386][ T8416] asm_exc_general_protection (arch/x86/include/asm/idtentry.h:564)
...
> We are sorry that the testcase and reproducing steps are not available
> for this case. Hope the call trace can help to investigate, and we can
> also help to do further verification if needed. Thanks.
Luckily, it's a known issue.
https://lore.kernel.org/all/20221110203504.1985010-3-seanjc@google.com
prev parent reply other threads:[~2022-11-15 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 15:14 [tip:x86/mm] [x86/kasan] 9fd429c280: BUG:unable_to_handle_page_fault_for_address kernel test robot
2022-11-15 0:28 ` Sean Christopherson [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=Y3LdJni8+ye/soOV@google.com \
--to=seanjc@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ning.han@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=ryabinin.a.a@gmail.com \
--cc=x86@kernel.org \
--cc=yujie.liu@intel.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