From: syzbot <syzbot+97028e7ff04ca4e3d85f@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: upstream test error: BUG: using smp_processor_id() in preemptible code in corrupted
Date: Thu, 11 Jun 2020 03:38:12 -0700 [thread overview]
Message-ID: <000000000000a8723f05a7cc8e14@google.com> (raw)
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@syzkaller.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@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2020-06-11 10:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000a8723f05a7cc8e14@google.com \
--to=syzbot+97028e7ff04ca4e3d85f@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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).