linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Kernel panic - not syncing: corrupted stack end detected inside scheduler
@ 2018-11-13 21:28 Qian Cai
  0 siblings, 0 replies; 2+ messages in thread
From: Qian Cai @ 2018-11-13 21:28 UTC (permalink / raw)
  To: linux-kernel; +Cc: selinux, Paul Moore, Stephen Smalley, Eric Paris

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!

^ permalink raw reply	[flat|nested] 2+ messages in thread
* Kernel panic - not syncing: corrupted stack end detected inside scheduler
@ 2018-11-13  4:45 Qian Cai
  0 siblings, 0 replies; 2+ messages in thread
From: Qian Cai @ 2018-11-13  4:45 UTC (permalink / raw)
  To: linux kernel; +Cc: linux-mm

Running LTP oom01 [1] test triggered kernel panic on an aarch64 server with the latest mainline (rc2).

[1] https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/mem/oom/oom01.c

[ 3433.338741] Kernel panic - not syncing: corrupted stack end detected inside scheduler
[ 3433.347644] CPU: 49 PID: 2189 Comm: in:imjournal Kdump: loaded Tainted: G        W         4.20.0-rc2+ #15
[ 3433.357298] Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.50 06/01/2018
[ 3433.364523] Call trace:
[ 3433.366993]  dump_backtrace+0x0/0x2c8
[ 3433.370659]  show_stack+0x24/0x30
[ 3433.373980]  dump_stack+0x118/0x19c
[ 3433.377473]  panic+0x1b8/0x31c
[ 3433.380530]  schedule+0x0/0x240
[ 3433.383672]  schedule+0xdc/0x240
[ 3433.386905]  io_schedule+0x24/0x48
[ 3433.390313]  get_request+0x3b0/0xb68
[ 3433.393891]  blk_queue_bio+0x3a4/0xcd8
[ 3433.397642]  generic_make_request+0x440/0x7d8
[ 3433.402000]  submit_bio+0xbc/0x300
[ 3433.405409]  __swap_writepage+0xa54/0xd00
[ 3433.409420]  swap_writepage+0x44/0xb0
[ 3433.413086]  pageout.isra.12+0x580/0xd80
[ 3433.417011]  shrink_page_list+0x2480/0x36f0
[ 3433.421196]  shrink_inactive_list+0x388/0xb98
[ 3433.425555]  shrink_node_memcg+0x344/0x9c0
[ 3433.429653]  shrink_node+0x200/0x940
[ 3433.433231]  do_try_to_free_pages+0x234/0x7d0
[ 3433.437589]  try_to_free_pages+0x228/0x6b0
[ 3433.441689]  __alloc_pages_nodemask+0xcbc/0x2028
[ 3433.446309]  alloc_pages_vma+0x1a4/0x208
[ 3433.450235]  __read_swap_cache_async+0x4fc/0x858
[ 3433.454855]  read_swap_cache_async+0xa4/0x100
[ 3433.459214]  swap_cluster_readahead+0x598/0x650
[ 3433.463746]  shmem_swapin+0xd4/0x150
[ 3433.467324]  shmem_getpage_gfp+0xf50/0x1c48
[ 3433.471509]  shmem_fault+0x140/0x340
[ 3433.475086]  __do_fault+0xd0/0x440
[ 3433.478490]  do_fault+0x54c/0xf48
[ 3433.481807]  __handle_mm_fault+0x4c0/0x928
[ 3433.485905]  handle_mm_fault+0x30c/0x4b8
[ 3433.489832]  do_page_fault+0x294/0x658
[ 3433.493584]  do_translation_fault+0x98/0xa8
[ 3433.497769]  do_mem_abort+0x64/0xf0
[ 3433.501258]  el0_da+0x24/0x28

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-11-13 21:29 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-11-13 21:28 Kernel panic - not syncing: corrupted stack end detected inside scheduler Qian Cai
  -- strict thread matches above, loose matches on Subject: below --
2018-11-13  4:45 Qian Cai

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).