From: Sean Christopherson <seanjc@google.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>, kvm list <kvm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, Shuah Khan <shuah@kernel.org>,
Maxim Levitsky <mlevitsk@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: WARNING: at arch/x86/kvm/../../../virt/kvm/kvm_main.c:3156 mark_page_dirty_in_slot
Date: Tue, 29 Mar 2022 16:17:28 +0000 [thread overview]
Message-ID: <YkMxGLAG0zqEzt1V@google.com> (raw)
In-Reply-To: <CA+G9fYsd+zXJqsxuYkWLQo0aYwmqLVA_YeBu+sr546bGA+1Nfg@mail.gmail.com>
On Tue, Mar 29, 2022, Naresh Kamboju wrote:
> While running kselftest kvm test cases on x86_64 devices the following
> kernel warning was reported.
...
> [ 62.510388] ------------[ cut here ]------------
> [ 62.515064] WARNING: CPU: 1 PID: 915 at
> arch/x86/kvm/../../../virt/kvm/kvm_main.c:3156
> mark_page_dirty_in_slot+0xba/0xd0
> [ 62.525968] Modules linked in: x86_pkg_temp_thermal fuse
> [ 62.531307] CPU: 1 PID: 915 Comm: hyperv_clock Not tainted 5.17.0 #1
> [ 62.537691] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
> 2.0b 07/27/2017
> [ 62.545185] RIP: 0010:mark_page_dirty_in_slot+0xba/0xd0
Long known issue. I think we're all waiting for someone else to post an actual
patch.
Vitaly, can you formally post the below patch, or do you need feedback first?
https://lore.kernel.org/all/874k51eddp.fsf@redhat.com/
next prev parent reply other threads:[~2022-03-29 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 15:20 WARNING: at arch/x86/kvm/../../../virt/kvm/kvm_main.c:3156 mark_page_dirty_in_slot Naresh Kamboju
2022-03-29 16:17 ` Sean Christopherson [this message]
2022-04-07 14:01 ` Vitaly Kuznetsov
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=YkMxGLAG0zqEzt1V@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mlevitsk@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox