From: Jiri Slaby <jirislaby@kernel.org>
To: Thomas Gleixner <tglx@kernel.org>, Peter Zijlstra <peterz@infradead.org>
Cc: "Matthieu Baerts" <matttbe@kernel.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
kvm@vger.kernel.org, virtualization@lists.linux.dev,
Netdev <netdev@vger.kernel.org>,
rcu@vger.kernel.org, "MPTCP Linux" <mptcp@lists.linux.dev>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"Shinichiro Kawasaki" <shinichiro.kawasaki@wdc.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"luto@kernel.org" <luto@kernel.org>,
"Michal Koutný" <MKoutny@suse.com>,
"Waiman Long" <longman@redhat.com>
Subject: Re: Stalls when starting a VSOCK listening socket: soft lockups, RCU stalls, timeout
Date: Thu, 5 Mar 2026 18:33:11 +0100 [thread overview]
Message-ID: <47cba228-bba7-4e58-a69d-ea41f8de6602@kernel.org> (raw)
In-Reply-To: <87zf4m2qvo.ffs@tglx>
On 05. 03. 26, 17:16, Thomas Gleixner wrote:
>> Dump of any other's mm_cids needed?
>
> It would be helpful to see the content of all PCPU CIDs and
> tsk::mm_cid::* for all tasks which belong to that process.
Not sure which of the two processes. So both:
crash> rd __per_cpu_offset 4
ffffffff94c38160: ffff8cc799a6c000 ffff8cc799aec000 ................
ffffffff94c38170: ffff8cc799b6c000 ffff8cc799bec000 ................
====== PID 7680 (spinning in mm_get_cid()) ======
4 tasks with
mm = 0xffff8cc406824680
mm_cid.pcpu = 0x66222619df00,
crash> task -x -R mm_cid ffff8cc4038525c0 ffff8cc40ad40000
ffff8cc40683cb80 ffff8cc418424b80
PID: 7680 TASK: ffff8cc4038525c0 CPU: 1 COMMAND: "asm"
mm_cid = {
active = 0x1,
cid = 0x80000000
},
PID: 7681 TASK: ffff8cc40ad40000 CPU: 3 COMMAND: "asm"
mm_cid = {
active = 0x1,
cid = 0x40000000
},
PID: 7682 TASK: ffff8cc40683cb80 CPU: 0 COMMAND: "asm"
mm_cid = {
active = 0x1,
cid = 0x40000002
},
PID: 7684 TASK: ffff8cc418424b80 CPU: 2 COMMAND: "asm"
mm_cid = {
active = 0x1,
cid = 0x40000001
},
crash> struct mm_cid_pcpu -x 0xfffff2e9bfc09f00
struct mm_cid_pcpu {
cid = 0x40000002
}
crash> struct mm_cid_pcpu -x 0xfffff2e9bfc89f00
struct mm_cid_pcpu {
cid = 0x0
}
crash> struct mm_cid_pcpu -x 0xfffff2e9bfd09f00
struct mm_cid_pcpu {
cid = 0x40000001
}
crash> struct mm_cid_pcpu -x 0xfffff2e9bfd89f00
struct mm_cid_pcpu {
cid = 0x40000000
}
====== PID 7508 (sleeping, holding the rq lock) ======
6 tasks with
mm = 0xffff8cc407222340
mm_cid.pcpu = 0x66222619df40,
crash> task -x -R mm_cid ffff8cc43d090000 ffff8cc43d094b80
ffff8cc494a00000 ffff8cc494a04b80 ffff8cc4038b8000 ffff8cc4038bcb80
PID: 7504 TASK: ffff8cc43d090000 CPU: 0 COMMAND: "compile"
mm_cid = {
active = 0x1,
cid = 0x40000001
},
PID: 7505 TASK: ffff8cc43d094b80 CPU: 1 COMMAND: "compile"
mm_cid = {
active = 0x1,
cid = 0x40000003
},
PID: 7506 TASK: ffff8cc494a00000 CPU: 3 COMMAND: "compile"
mm_cid = {
active = 0x1,
cid = 0x40000000
},
PID: 7507 TASK: ffff8cc494a04b80 CPU: 2 COMMAND: "compile"
mm_cid = {
active = 0x1,
cid = 0x40000002
},
PID: 7508 TASK: ffff8cc4038b8000 CPU: 1 COMMAND: "compile"
mm_cid = {
active = 0x1,
cid = 0x40000003
},
PID: 7630 TASK: ffff8cc4038bcb80 CPU: 2 COMMAND: "compile"
mm_cid = {
active = 0x1,
cid = 0x40000002
},
crash> struct mm_cid_pcpu -x 0xfffff2e9bfc09f40
struct mm_cid_pcpu {
cid = 0x40000001
}
crash> struct mm_cid_pcpu -x 0xfffff2e9bfc89f40
struct mm_cid_pcpu {
cid = 0x40000003
}
crash> struct mm_cid_pcpu -x 0xfffff2e9bfd09f40
struct mm_cid_pcpu {
cid = 0x40000002
}
crash> struct mm_cid_pcpu -x 0xfffff2e9bfd89f40
struct mm_cid_pcpu {
cid = 0x40000000
}
Anything else :)?
--
js
suse labs
next prev parent reply other threads:[~2026-03-05 17:33 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 11:54 Stalls when starting a VSOCK listening socket: soft lockups, RCU stalls, timeout Matthieu Baerts
2026-02-06 16:38 ` Stefano Garzarella
2026-02-06 17:13 ` Matthieu Baerts
2026-02-26 10:37 ` Jiri Slaby
2026-03-02 5:28 ` Jiri Slaby
2026-03-02 11:46 ` Peter Zijlstra
2026-03-02 14:30 ` Waiman Long
2026-03-05 7:00 ` Jiri Slaby
2026-03-05 11:53 ` Jiri Slaby
2026-03-05 12:20 ` Jiri Slaby
2026-03-05 16:16 ` Thomas Gleixner
2026-03-05 17:33 ` Jiri Slaby [this message]
2026-03-05 19:25 ` Thomas Gleixner
2026-03-06 5:48 ` Jiri Slaby
2026-03-06 9:57 ` Thomas Gleixner
2026-03-06 10:16 ` Jiri Slaby
2026-03-06 16:28 ` Thomas Gleixner
2026-03-06 11:06 ` Matthieu Baerts
2026-03-06 16:57 ` Matthieu Baerts
2026-03-06 18:31 ` Jiri Slaby
2026-03-06 18:44 ` Matthieu Baerts
2026-03-06 21:40 ` Matthieu Baerts
2026-03-06 15:24 ` Peter Zijlstra
2026-03-07 9:01 ` Thomas Gleixner
2026-03-07 22:29 ` Thomas Gleixner
2026-03-08 9:15 ` Thomas Gleixner
2026-03-08 16:55 ` Jiri Slaby
2026-03-08 16:58 ` Thomas Gleixner
2026-03-08 17:23 ` Matthieu Baerts
2026-03-09 8:43 ` Thomas Gleixner
2026-03-09 12:23 ` Matthieu Baerts
2026-03-10 8:09 ` Thomas Gleixner
2026-03-10 8:20 ` Thomas Gleixner
2026-03-10 8:56 ` Jiri Slaby
2026-03-10 9:00 ` Jiri Slaby
2026-03-10 10:03 ` Thomas Gleixner
2026-03-10 10:06 ` Thomas Gleixner
2026-03-10 11:24 ` Matthieu Baerts
2026-03-10 11:54 ` Peter Zijlstra
2026-03-10 12:28 ` Thomas Gleixner
2026-03-10 13:40 ` Matthieu Baerts
2026-03-10 13:47 ` Thomas Gleixner
2026-03-10 15:51 ` Matthieu Baerts
2026-03-03 13:23 ` Matthieu Baerts
2026-03-05 6:46 ` Jiri Slaby
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=47cba228-bba7-4e58-a69d-ea41f8de6602@kernel.org \
--to=jirislaby@kernel.org \
--cc=MKoutny@suse.com \
--cc=dave.hansen@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=luto@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=stefanha@redhat.com \
--cc=tglx@kernel.org \
--cc=virtualization@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 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.