[<prev] [next>] [day] [month] [year] [list]
Message-ID: <000000000000a8723f05a7cc8e14@google.com>
Date: Thu, 11 Jun 2020 03:38:12 -0700
From: syzbot <syzbot+97028e7ff04ca4e3d85f@...kaller.appspotmail.com>
To: adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
tytso@....edu
Subject: upstream test error: BUG: using smp_processor_id() in preemptible
code in corrupted
Hello,
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: https://syzkaller.appspot.com/x/log.txt?x=17e35a36100000
kernel config: https://syzkaller.appspot.com/x/.config?x=28f5490cd437fcf
dashboard link: https://syzkaller.appspot.com/bug?extid=97028e7ff04ca4e3d85f
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+97028e7ff04ca4e3d85f@...kaller.appspotmail.com
[.[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
nges.
[.[0;32m OK .[0m] Started Load/Save RF Kill Switch Status.
Debian GNU/Linux 9 syzkaller ttyS0
Warning: Permanently added '10.128.0.243' (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 10.128.0.26:39073
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 https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@...glegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
Powered by blists - more mailing lists