syzbot


linux-next test error: BUG: using smp_processor_id() in preemptible code in corrupted

Status: closed as invalid on 2020/06/11 07:47
Subsystems: ext4
[Documentation on labels]
First crash: 1415d, last: 1415d

Sample crash report:
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
         Starting Load/Save RF Kill Switch Status...
[  OK  ] Started Upda[   54.686301][ T6726] BUG: using smp_processor_id() in preemptible [00000000] code: systemd-rfkill/6726
te UTMP about Sy[   54.695843][ T6726] caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711
stem Runlevel Ch[   54.703216][ T6726] CPU: 0 PID: 6726 Comm: systemd-rfkill Not tainted 5.7.0-next-20200611-syzkaller #0
anges.
[  OK  ] Started Load/Save RF Kill Switch Status.

Debian GNU/Linux 9 syzkaller ttyS0

Warning: Permanently added '10.128.0.143' (ECDSA) to the list of known hosts.
2020/06/11 04:12:28 fuzzer started
2020/06/11 04:12:28 connecting to host at 10.128.0.26:42335
2020/06/11 04:12:28 checking machine...
2020/06/11 04:12:28 checking revisions...
2020/06/11 04:12:28 testing simple program...
2020/06/11 04:12:29 building call list...
executing program

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/06/11 04:12 linux-next 192e08e14e37 a6f7998d .config console log report ci-upstream-linux-next-kasan-gce-root
* Struck through repros no longer work on HEAD.