syzbot


kernel panic: Attempted to kill init! (2)

Status: closed as invalid on 2017/12/28 09:40
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+bab350dcd3afb1945f4b@syzkaller.appspotmail.com
First crash: 2410d, last: 2404d
Discussions (1)
Title Replies (including bot) Last reply
kernel panic: Attempted to kill init! (2) 1 (2) 2017/12/28 09:40
Similar bugs (14)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-15 kernel panic: Attempted to kill init! origin:upstream missing-backport C error 407 17h10m 648d 0/2 premoderation: reported C repro on 2022/10/13 06:16
upstream kernel panic: Attempted to kill init! (5) kernel C done inconclusive 9 964d 1204d 0/27 auto-closed as invalid on 2022/09/05 15:05
android-49 kernel panic: Attempted to kill init! (2) syz 1 2446d 2446d 0/3 closed as invalid on 2017/12/06 10:59
upstream kernel panic: Attempted to kill init! C 1 2539d 2539d 0/27 closed as invalid on 2017/08/11 14:48
linux-4.14 kernel panic: Attempted to kill init! C 1 513d 618d 0/1 upstream: reported C repro on 2022/11/11 22:11
android-49 kernel panic: Attempted to kill init! C 1 2507d 2507d 0/3 closed as invalid on 2017/09/12 18:13
upstream kernel panic: Attempted to kill init! (6) kernel 2 452d 463d 0/27 auto-obsoleted due to no activity on 2023/07/25 19:19
android-54 kernel panic: Attempted to kill init! C 1 1422d 1422d 0/2 auto-obsoleted due to no activity on 2023/04/14 11:56
upstream kernel panic: Attempted to kill init! (4) kernel C done 19 1588d 2204d 0/27 closed as invalid on 2020/03/18 10:26
upstream kernel panic: Attempted to kill init! (3) kernel C 9 2284d 2396d 0/27 closed as invalid on 2018/06/14 08:46
android-414 kernel panic: Attempted to kill init! C 3 1820d 1930d 0/1 public: reported C repro on 2019/04/10 16:04
android-5-10 kernel panic: Attempted to kill init! C error 648 1d01h 444d 0/2 premoderation: reported C repro on 2023/05/05 07:30
android-44 kernel panic: Attempted to kill init! C 8 2064d 1927d 0/2 public: reported C repro on 2019/04/13 00:00
android-49 kernel panic: Attempted to kill init! (3) C 22 1820d 1927d 0/3 public: reported C repro on 2019/04/13 00:00

Sample crash report:
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

CPU: 1 PID: 1 Comm: init Not tainted 4.15.0-rc3-next-20171214+ #67
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0xe9/0x14b lib/dump_stack.c:53
 panic+0x10e/0x2f8 kernel/panic.c:183
 find_child_reaper kernel/exit.c:578 [inline]
 forget_original_parent kernel/exit.c:674 [inline]
 exit_notify kernel/exit.c:710 [inline]
 do_exit+0x1045/0x1050 kernel/exit.c:889
 do_group_exit+0x60/0x100 kernel/exit.c:972
 get_signal+0x36c/0xad0 kernel/signal.c:2337
 do_signal+0x23/0x670 arch/x86/kernel/signal.c:809
 exit_to_usermode_loop+0x13c/0x160 arch/x86/entry/common.c:161
 prepare_exit_to_usermode+0x102/0x110 arch/x86/entry/common.c:195
 retint_user+0x8/0x18
RIP: 0033:          (null)
RSP: 002b:00007ffe8c9df0b0 EFLAGS: 00010286
RAX: ffffffffffffffff

Crashes (347):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2017/12/20 05:29 linux-next 6084b576dca2 2d836b1d .config console log report syz ci-upstream-next-kasan-gce
2017/12/21 21:30 upstream 9035a8961b50 eaadba98 .config console log report ci-upstream-kasan-gce
2017/12/19 01:14 upstream 1291a0d5049d 1c4160ef .config console log report ci-upstream-kasan-gce
2017/12/18 15:43 upstream 1291a0d5049d 1c4160ef .config console log report ci-upstream-kasan-gce
2017/12/18 14:25 upstream 1291a0d5049d 1c4160ef .config console log report ci-upstream-kasan-gce
2017/12/18 13:51 upstream 1291a0d5049d d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/18 12:04 upstream 1291a0d5049d d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/18 09:50 upstream b9f5fb1800d8 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/18 09:09 upstream b9f5fb1800d8 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/18 07:09 upstream b9f5fb1800d8 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/18 04:39 upstream b9f5fb1800d8 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/18 01:55 upstream b9f5fb1800d8 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/18 00:03 upstream b9f5fb1800d8 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/17 23:21 upstream b9f5fb1800d8 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/17 21:42 upstream b9f5fb1800d8 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/17 21:18 upstream f3b5ad89de16 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/17 19:55 upstream f3b5ad89de16 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/17 18:53 upstream f3b5ad89de16 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/17 18:33 upstream f3b5ad89de16 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/17 18:32 upstream f3b5ad89de16 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/17 16:33 upstream f3b5ad89de16 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/17 16:05 upstream f3b5ad89de16 d5beb42a .config console log report ci-upstream-kasan-gce
2017/12/20 06:26 linux-next 6084b576dca2 2d836b1d .config console log report ci-upstream-next-kasan-gce
2017/12/19 14:24 linux-next 6084b576dca2 af9163c7 .config console log report ci-upstream-next-kasan-gce
2017/12/18 17:39 mmots 82bcf1def3b5 1c4160ef .config console log report ci-upstream-mmots-kasan-gce
2017/12/18 14:29 linux-next 6084b576dca2 1c4160ef .config console log report ci-upstream-next-kasan-gce
2017/12/18 11:14 mmots 82bcf1def3b5 d5beb42a .config console log report ci-upstream-mmots-kasan-gce
2017/12/18 10:14 linux-next 6084b576dca2 d5beb42a .config console log report ci-upstream-next-kasan-gce
2017/12/18 09:59 linux-next 6084b576dca2 d5beb42a .config console log report ci-upstream-next-kasan-gce
2017/12/18 09:47 mmots 82bcf1def3b5 d5beb42a .config console log report ci-upstream-mmots-kasan-gce
2017/12/18 09:20 linux-next 6084b576dca2 d5beb42a .config console log report ci-upstream-next-kasan-gce
2017/12/18 07:24 linux-next 6084b576dca2 d5beb42a .config console log report ci-upstream-next-kasan-gce
2017/12/18 07:08 mmots 82bcf1def3b5 d5beb42a .config console log report ci-upstream-mmots-kasan-gce
2017/12/18 06:59 mmots 82bcf1def3b5 d5beb42a .config console log report ci-upstream-mmots-kasan-gce
2017/12/18 05:04 linux-next 6084b576dca2 d5beb42a .config console log report ci-upstream-next-kasan-gce
2017/12/18 04:45 mmots 82bcf1def3b5 d5beb42a .config console log report ci-upstream-mmots-kasan-gce
2017/12/18 00:28 mmots 82bcf1def3b5 d5beb42a .config console log report ci-upstream-mmots-kasan-gce
2017/12/17 18:52 linux-next 6084b576dca2 d5beb42a .config console log report ci-upstream-next-kasan-gce
2017/12/17 18:37 mmots 82bcf1def3b5 d5beb42a .config console log report ci-upstream-mmots-kasan-gce
2017/12/17 18:21 linux-next 6084b576dca2 d5beb42a .config console log report ci-upstream-next-kasan-gce
2017/12/17 16:05 linux-next 6084b576dca2 d5beb42a .config console log report ci-upstream-next-kasan-gce
* Struck through repros no longer work on HEAD.