kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
	mm <linux-mm@kvack.org>,
	yuzhao@google.com, Michal Hocko <MHocko@suse.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	shy828301@gmail.com
Subject: Re: Stalls in qemu with host running 6.1 (everything stuck at mmap_read_lock())
Date: Thu, 12 Jan 2023 16:43:08 +0100	[thread overview]
Message-ID: <17b584f1-9d3b-35bb-7035-9b225936fd23@kernel.org> (raw)
In-Reply-To: <7aa90802-d25c-baa3-9c03-2502ad3c708a@kernel.org>

On 12. 01. 23, 7:07, Jiri Slaby wrote:
> I have rebooted to a fresh kernel which 1) have lockdep enabled, and 2) 
> I have debuginfo for. So next time this happens, I can print held locks 

For the time being:

 >  Showing all locks held in the system:
 >  1 lock held by rcu_tasks_kthre/11:
 >   #0: ffffffffb097a550 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: 
rcu_tasks_one_gp+0x2b/0x3d0
 >  1 lock held by rcu_tasks_rude_/12:
 >   #0: ffffffffb097a2d0 (rcu_tasks_rude.tasks_gp_mutex){+.+.}-{3:3}, 
at: rcu_tasks_one_gp+0x2b/0x3d0
 >  1 lock held by rcu_tasks_trace/13:
 >   #0: ffffffffb097a010 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, 
at: rcu_tasks_one_gp+0x2b/0x3d0
 >  1 lock held by in:imklog/1308:
 >   #0: ffff9538d81364e8 (&f->f_pos_lock){+.+.}-{3:3}, at: 
__fdget_pos+0x4c/0x60
 >  2 locks held by plasmashell/6865:
 >   #0: ffff95393f6092e8 (&f->f_pos_lock){+.+.}-{3:3}, at: 
__fdget_pos+0x4c/0x60
 >   #1: ffff9538dc2aa458 (&mm->mmap_lock#2){++++}-{3:3}, at: 
__access_remote_vm+0x4f/0x3c0
 >  1 lock held by fuse mainloop/9772:
 >   #0: ffff953a578a7468 (&pipe->mutex/1){+.+.}-{3:3}, at: 
splice_file_to_pipe+0x26/0xd0
 >  1 lock held by fuse mainloop/9773:
 >   #0: ffff953a578a7e68 (&pipe->mutex/1){+.+.}-{3:3}, at: 
splice_file_to_pipe+0x26/0xd0
 >  1 lock held by fuse mainloop/25378:
 >   #0: ffff9538d3d8c868 (&pipe->mutex/1){+.+.}-{3:3}, at: 
splice_file_to_pipe+0x26/0xd0
 >  1 lock held by qemu-kvm/31097:
 >  6 locks held by qemu-kvm/31098:
 >   #0: ffff953a062080b0 (&vcpu->mutex){+.+.}-{3:3}, at: 
kvm_vcpu_ioctl+0x77/0x6d0 [kvm]
 >   #1: ffff9538c6e838e8 (&serio->lock){-.-.}-{2:2}, at: 
serio_interrupt+0x24/0x90
 >   #2: ffff9538c6e80230 (&dev->event_lock){-.-.}-{2:2}, at: 
input_event+0x3c/0x80
 >   #3: ffffffffb097af60 (rcu_read_lock){....}-{1:2}, at: 
input_pass_values.part.0+0x5/0x270
 >   #4: ffffffffb097af60 (rcu_read_lock){....}-{1:2}, at: 
__handle_sysrq+0x5/0xa0
 >   #5: ffffffffb097af60 (rcu_read_lock){....}-{1:2}, at: 
debug_show_all_locks+0x15/0x16b
 >  1 lock held by qemu-kvm/31099:
 >  3 locks held by qemu-kvm/31100:
 >  1 lock held by qemu-kvm/31819:
 >   #0: ffff9538dc2aa458 (&mm->mmap_lock#2){++++}-{3:3}, at: 
__vm_munmap+0x95/0x170
 >  1 lock held by qemu-kvm/31935:
 >   #0: ffff9538dc2aa458 (&mm->mmap_lock#2){++++}-{3:3}, at: 
do_madvise.part.0+0xe8/0x2a0
 >  1 lock held by dmesg/31873:
 >   #0: ffff9538ef6000d0 (&user->lock){+.+.}-{3:3}, at: 
devkmsg_read+0x4b/0x230
 >  1 lock held by ps/31996:
 >   #0: ffff9538dc2aa458 (&mm->mmap_lock#2){++++}-{3:3}, at: 
__access_remote_vm+0x4f/0x3c0


> and dump a kcore (kdump is set up).

Going to trigger a dump now.

-- 
js
suse labs


  parent reply	other threads:[~2023-01-12 15:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11  8:00 Stalls in qemu with host running 6.1 (everything stuck at mmap_read_lock()) Jiri Slaby
2023-01-11  8:23 ` Vlastimil Babka
2023-01-11  8:31 ` Michal Hocko
2023-01-11  9:21 ` Linux kernel regression tracking (#adding)
2023-01-19 14:58   ` Vlastimil Babka
2023-01-11 22:50 ` Paolo Bonzini
2023-01-12  0:37 ` Pedro Falcato
2023-01-12  6:07   ` Jiri Slaby
2023-01-12 10:31     ` Maxim Levitsky
2023-01-12 10:35       ` Vlastimil Babka
2023-01-12 15:43     ` Jiri Slaby [this message]
2023-01-12 16:57       ` Jiri Slaby
2023-01-13 17:14         ` Liam Howlett
2023-01-12  8:23   ` Yu Zhao
2023-01-13 17:27     ` Liam Howlett

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=17b584f1-9d3b-35bb-7035-9b225936fd23@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=MHocko@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pbonzini@redhat.com \
    --cc=pedro.falcato@gmail.com \
    --cc=shy828301@gmail.com \
    --cc=vbabka@suse.cz \
    --cc=yuzhao@google.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;
as well as URLs for NNTP newsgroup(s).