From: Sean Christopherson <seanjc@google.com>
To: Peter Xu <peterx@redhat.com>
Cc: Nikunj A Dadhania <nikunj@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
vasant.hegde@amd.com, brijesh.singh@amd.com
Subject: Re: [PATCH v2] KVM: x86: Check for rmaps allocation
Date: Fri, 7 Jan 2022 17:01:10 +0000 [thread overview]
Message-ID: <Ydhx1qguxVZxOGfo@google.com> (raw)
In-Reply-To: <YdVfvp2Pw6JUR61K@xz-m1.local>
On Wed, Jan 05, 2022, Peter Xu wrote:
> On Wed, Jan 05, 2022 at 09:33:37AM +0530, Nikunj A Dadhania wrote:
> > With TDP MMU being the default now, access to mmu_rmaps_stat debugfs
> > file causes following oops:
> >
> > BUG: kernel NULL pointer dereference, address: 0000000000000000
> > PGD 0 P4D 0
> > Oops: 0000 [#1] PREEMPT SMP NOPTI
> > CPU: 7 PID: 3185 Comm: cat Not tainted 5.16.0-rc4+ #204
> > RIP: 0010:pte_list_count+0x6/0x40
> > Call Trace:
> > <TASK>
> > ? kvm_mmu_rmaps_stat_show+0x15e/0x320
> > seq_read_iter+0x126/0x4b0
> > ? aa_file_perm+0x124/0x490
> > seq_read+0xf5/0x140
> > full_proxy_read+0x5c/0x80
> > vfs_read+0x9f/0x1a0
> > ksys_read+0x67/0xe0
> > __x64_sys_read+0x19/0x20
> > do_syscall_64+0x3b/0xc0
> > entry_SYSCALL_64_after_hwframe+0x44/0xae
> > RIP: 0033:0x7fca6fc13912
> >
> > Return early when rmaps are not present.
> >
> > Reported-by: Vasant Hegde <vasant.hegde@amd.com>
> > Tested-by: Vasant Hegde <vasant.hegde@amd.com>
> > Signed-off-by: Nikunj A Dadhania <nikunj@amd.com>
> > ---
Reviewed-by: Sean Christopherson <seanjc@google.com>
next prev parent reply other threads:[~2022-01-07 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 4:03 [PATCH v2] KVM: x86: Check for rmaps allocation Nikunj A Dadhania
2022-01-05 9:07 ` Peter Xu
2022-01-07 17:01 ` Sean Christopherson [this message]
2022-01-07 17:03 ` Paolo Bonzini
2022-01-07 17:04 ` Paolo Bonzini
2022-01-07 17:08 ` Paolo Bonzini
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=Ydhx1qguxVZxOGfo@google.com \
--to=seanjc@google.com \
--cc=brijesh.singh@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=vasant.hegde@amd.com \
--cc=vkuznets@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.