kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 201149] kvm vhost cause kernel crash on CentOS 7.2.1511
Date: Wed, 14 Jul 2021 02:02:32 +0000	[thread overview]
Message-ID: <bug-201149-28872-N8DAXzYVWx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201149-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=201149

Li Zhijian (lizhijian@cn.fujitsu.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lizhijian@cn.fujitsu.com

--- Comment #1 from Li Zhijian (lizhijian@cn.fujitsu.com) ---
I had a similar calltrace with 3.10.0-327 kernel where some logs indicate:

[53012179.742195] Oops: 0002 [#1] SMP 
...
[53012181.153015] RIP: 0010:[<ffffffff810b192e>]  [<ffffffff810b192e>]
dequeue_task+0x5e/0xa0

crash> dis -l dequeue_task+94 5
0xffffffff810b192e <dequeue_task+94>:   add    $0x10,%rsp
0xffffffff810b1932 <dequeue_task+98>:   pop    %rbx
0xffffffff810b1933 <dequeue_task+99>:   pop    %rbp
0xffffffff810b1934 <dequeue_task+100>:  retq   
0xffffffff810b1935 <dequeue_task+101>:  nopl   (%rax)

but the assembly isn't a memorry access which is not consistent with where
'Oops: 0002' said.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

           reply	other threads:[~2021-07-14  2:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-201149-28872@https.bugzilla.kernel.org/>]

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=bug-201149-28872-N8DAXzYVWx@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    /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).