From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
regressions@lists.linux.dev, lkft-triage@lists.linaro.org,
Marco Elver <elver@google.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-perf-users@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: qemu-i386: perf: BUG: kernel NULL pointer dereference, address: 00000148
Date: Thu, 3 Nov 2022 15:23:00 +0530 [thread overview]
Message-ID: <6d78caf0-cb4c-1a30-66ce-242df87656ef@amd.com> (raw)
In-Reply-To: <CA+G9fYsGFoC5TciCuijZXLx48TZnoTSkq=iUgb+vFdi9EYTucw@mail.gmail.com>
> [ 116.006600] BUG: kernel NULL pointer dereference, address: 00000148
> [ 116.008309] #PF: supervisor read access in kernel mode
> [ 116.009527] #PF: error_code(0x0000) - not-present page
> [ 116.010809] *pde = 00000000
> [ 116.011454] Oops: 0000 [#1] PREEMPT SMP
> [ 116.012144] CPU: 2 PID: 449 Comm: perf-exec Not tainted 6.0.7-rc1 #1
> [ 116.013256] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
> BIOS 1.12.0-1 04/01/2014
> [ 116.014710] EIP: x86_pmu_enable_event+0x4a/0x190
> [ 116.015617] Code: 64 a1 10 2c 8d c6 85 c0 75 16 8b 5d f4 8b 75 f8
> 8b 7d fc 89 ec 5d c3 8d b4 26 00 00 00 00 66 90 b8 43 bb 49 c6 e8 56
> 13 fb 00 <8b> b3 48 01 00 00 b8 dc 39 8d c6 64 03 05 b0 28 8d c6 8b 38
> 85 f6
> [ 116.018642] EAX: 00000002 EBX: 00000000 ECX: c0010200 EDX: c649bb43
> [ 116.019709] ESI: f51c6b00 EDI: f51c6c00 EBP: c34e1da4 ESP: c34e1d88
> [ 116.020744] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00210002
> [ 116.021847] CR0: 80050033 CR2: 00000148 CR3: 03e07000 CR4: 003506d0
> [ 116.022930] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> [ 116.023674] DR6: ffff4ff0 DR7: 00000400
> [ 116.024078] Call Trace:
> [ 116.024348] amd_pmu_enable_all+0x3d/0x50
> [ 116.024776] x86_pmu_enable+0x17c/0x370
> [ 116.025179] ctx_resched+0xad/0xf0
> [ 116.025542] perf_event_exec+0x338/0x400
> [ 116.025956] begin_new_exec+0x548/0xac0
> [ 116.026358] load_elf_binary+0x2ad/0x1360
> [ 116.027063] ? __kernel_read+0x12c/0x220
> [ 116.027520] ? _raw_read_unlock+0x1d/0x40
> [ 116.027957] ? load_misc_binary+0x1eb/0x290
> [ 116.028404] ? trace_preempt_on+0x29/0xe0
> [ 116.028827] ? load_misc_binary+0x1eb/0x290
> [ 116.029287] ? preempt_count_sub+0xc1/0x110
> [ 116.029722] ? bprm_execve+0x256/0x650
> [ 116.030122] ? preempt_count_sub+0xc1/0x110
> [ 116.030600] bprm_execve+0x260/0x650
> [ 116.031006] do_execveat_common+0x13f/0x1b0
> [ 116.031482] __ia32_sys_execve+0x35/0x40
> [ 116.031897] __do_fast_syscall_32+0x4c/0xc0
> [ 116.032358] do_fast_syscall_32+0x32/0x70
> [ 116.032777] do_SYSENTER_32+0x15/0x20
> [ 116.033190] entry_SYSENTER_32+0x98/0xf1
> [ 116.033601] EIP: 0xb7eda549
> [ 116.033903] Code: Unable to access opcode bytes at RIP 0xb7eda51f.
> [ 116.034576] EAX: ffffffda EBX: bfa6d940 ECX: bfa730f8 EDX: 08ea9dc0
> [ 116.035278] ESI: bfa73d61 EDI: bfa6d949 EBP: bfa6da38 ESP: bfa6d918
> [ 116.035927] DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 007b EFLAGS: 00200296
> [ 116.036624] Modules linked in:
> [ 116.036961] CR2: 0000000000000148
> [ 116.037315] ---[ end trace 0000000000000000 ]---
Seems like same as:
https://lore.kernel.org/all/CA+G9fYtOP-spGS7gYyBB-8wpUDiKxd5e_Nk05J9gzWR_DLBeFA@mail.gmail.com
prev parent reply other threads:[~2022-11-03 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 13:12 Naresh Kamboju
2022-11-02 14:24 ` Thorsten Leemhuis
2022-11-02 21:25 ` Greg KH
2022-11-02 21:25 ` Greg KH
2022-11-03 5:32 ` Naresh Kamboju
2022-11-03 9:53 ` Ravi Bangoria [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=6d78caf0-cb4c-1a30-66ce-242df87656ef@amd.com \
--to=ravi.bangoria@amd.com \
--cc=acme@kernel.org \
--cc=ebiederm@xmission.com \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
/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®