From: Qian Cai <cai@gmx.us>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "selinux@vger.kernel.org" <selinux@vger.kernel.org>,
Paul Moore <paul@paul-moore.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>
Subject: Kernel panic - not syncing: corrupted stack end detected inside scheduler
Date: Tue, 13 Nov 2018 16:28:17 -0500 [thread overview]
Message-ID: <1542144497.12945.29.camel@gmx.us> (raw)
Running a runc testsuite [1] on an aarch64 server with the latest mainline (rc2)
triggered this,
[1] https://fedorapeople.org/cgit/caiqian/public_git/runctst.git/tree/runctst.py
=============
# python runctst.py
...
- start: runc ocf poststart
load container root: container "root" does not exist
container_linux.go:364: running poststart hook 0 caused "error running hook:
exit status 1, stdout: , stderr: "
- error: unexpected zero-size output.
- start: runc ocf mount dev
- pass: runc ocf mount dev
- start: runc ocf network
- pass: runc ocf network
- start: runc ocf args systemd
- error: unexpected dbus output is USER PID %CPU %MEM VSZ RSS
TTY STAT START TIME COMMAND
root 1 68.6 0.0 8832 7424 ? Rs 19:29 0:03 /usr/sbin/init
root 18 24.0 0.0 14848 8704 ? Ss 19:29 0:00
/usr/lib/systemd/systemd-journald
root 22 0.0 0.0 9728 6592 ? Rs 19:29 0:00 ps aux
==============
[ 2231.649459] Kernel panic - not syncing: corrupted stack end detected inside
scheduler
[ 2231.657307] CPU: 185 PID: 11718 Comm: dbus-daemon Kdump: loaded Tainted:
G W 4.20.0-rc2+ #4
[ 2231.666961] Hardware name: HPE Apollo 70 /C01_APACHE_MB ,
BIOS L50_5.13_1.0.6 07/10/2018
[ 2231.676788] Call trace:
[ 2231.679273] dump_backtrace+0x0/0x2c8
[ 2231.682950] show_stack+0x24/0x30
[ 2231.686273] dump_stack+0x118/0x19c
[ 2231.689765] panic+0x1b8/0x31c
[ 2231.692822] schedule+0x0/0x240
[ 2231.695963] preempt_schedule_common+0x3c/0x78
[ 2231.700406] _cond_resched+0xfc/0x108
[ 2231.704077] kmem_cache_alloc+0x2e0/0x3f8
[ 2231.708102] selinux_inode_alloc_security+0xc4/0x1b0
[ 2231.713080] security_inode_alloc+0x44/0x70
[ 2231.717267] inode_init_always+0x270/0x4b8
[ 2231.721364] alloc_inode+0x50/0xd0
[ 2231.724768] new_inode_pseudo+0x84/0x120
[ 2231.728691] sock_alloc+0x30/0x108
[ 2231.732093] __sock_create+0x154/0x560
[ 2231.735843] __sys_socket+0xc8/0x178
[ 2231.739429] __arm64_sys_socket+0x4c/0x60
[ 2231.743460] el0_svc_handler+0xd4/0x198
[ 2231.747295] el0_svc+0x8/0xc
[ 2231.750777] SMP: stopping secondary CPUs
[ 2231.757333] Starting crashdump kernel...
[ 2231.761260] Bye!
next reply other threads:[~2018-11-13 21:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 21:28 Qian Cai [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-19 11:23 Kernel panic - not syncing: corrupted stack end detected inside scheduler Andreas Schwab
2018-11-19 11:23 ` Andreas Schwab
2018-11-19 23:46 ` Palmer Dabbelt
2018-11-19 23:46 ` Palmer Dabbelt
2018-11-20 8:52 ` Andreas Schwab
2018-11-20 8:52 ` Andreas Schwab
2018-11-20 17:29 ` Palmer Dabbelt
2018-11-20 17:29 ` Palmer Dabbelt
2018-11-21 8:55 ` Andreas Schwab
2018-11-21 8:55 ` Andreas Schwab
2018-11-13 4:45 Qian Cai
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=1542144497.12945.29.camel@gmx.us \
--to=cai@gmx.us \
--cc=eparis@parisplace.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@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 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.