lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Thu, 11 Jun 2020 03:38:12 -0700
From:   syzbot <>
Subject: upstream test error: BUG: using smp_processor_id() in preemptible
 code in corrupted


syzbot found the following crash on:

HEAD commit:    84fc461d Merge tag 'for-linus-5.8-rc1' of git://git.kernel..
git tree:       upstream
console output:
kernel config:
dashboard link:
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)

IMPORTANT: if you fix the bug, please add the following tag to the commit:

[.[0;32m  OK  .[0m] Reached target Login Prompts.
[.[0;32m  OK  .[0m] Reached target Multi-User System.
[.[0;32m  OK  .[0m] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
         Starting Load/Save RF Kill Switch Status...
[.[0;32m  OK  .[0m] Started Updat[   68.080829][ T6736] BUG: using smp_processor_id() in preemptible [00000000] code: systemd-rfkill/6736
e UTMP about Sys[   68.090431][ T6736] caller is ext4_mb_new_blocks+0xa77/0x3b30 fs/ext4/mballoc.c:4711
tem Runlevel Cha[   68.098400][ T6736] CPU: 0 PID: 6736 Comm: systemd-rfkill Not tainted 5.7.0-syzkaller #0
[.[0;32m  OK  .[0m] Started Load/Save RF Kill Switch Status.

Debian GNU/Linux 9 syzkaller ttyS0

Warning: Permanently added '' (ECDSA) to the list of known hosts.
2020/06/10 20:51:27 fuzzer started
2020/06/10 20:51:27 connecting to host at
2020/06/10 20:51:27 checking machine...
2020/06/10 20:51:27 checking revisions...
2020/06/10 20:51:27 testing simple program...
2020/06/10 20:51:29 building call list...
executing program

This bug is generated by a bot. It may contain errors.
See for more information about syzbot.
syzbot engineers can be reached at

syzbot will keep track of this bug report. See: for how to communicate with syzbot.

Powered by blists - more mailing lists