From: Qian Cai <cai@gmx.us>
To: linux kernel <linux-kernel@vger.kernel.org>
Cc: linux-mm@kvack.org
Subject: Kernel panic - not syncing: corrupted stack end detected inside scheduler
Date: Mon, 12 Nov 2018 23:45:29 -0500 [thread overview]
Message-ID: <721E7B42-2D55-4866-9C1A-3E8D64F33F9C@gmx.us> (raw)
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
next reply other threads:[~2018-11-13 4:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 4:45 Qian Cai [this message]
2018-12-07 22:34 ` [PATCH] arm64: increase stack size for KASAN_EXTRA Qian Cai
2018-12-11 12:42 ` Arnd Bergmann
2018-12-11 17:18 ` Qian Cai
2018-12-11 21:43 ` Arnd Bergmann
2018-12-11 21:52 ` Qian Cai
2018-12-11 21:56 ` Arnd Bergmann
2018-12-11 21:59 ` Qian Cai
2018-12-11 22:12 ` Arnd Bergmann
2018-12-11 22:22 ` Qian Cai
2018-12-11 23:06 ` Arnd Bergmann
2018-12-12 3:54 ` Qian Cai
2018-11-13 21:28 Kernel panic - not syncing: corrupted stack end detected inside scheduler 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=721E7B42-2D55-4866-9C1A-3E8D64F33F9C@gmx.us \
--to=cai@gmx.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).