Hello,
syzbot found the following issue on:
HEAD commit: bf3e7628 Merge branch 'mtd/fixes' of git://
git.kernel.org/..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=1045d43a500000
kernel config:
https://syzkaller.appspot.com/x/.config?x=76dfc991796328d4
dashboard link:
https://syzkaller.appspot.com/bug?extid=056469a356e70d762b4f
compiler: clang version 12.0.0 (
https://github.com/llvm/llvm-project.git 913f6005669cfb590c99865a90bc51ed0983d09d)
CC: [
b...@alien8.de h...@zytor.com linux-...@vger.kernel.org lu...@kernel.org mi...@redhat.com tg...@linutronix.de x...@kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+056469...@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in do_syslog / do_syslog
write to 0xffffffff882f5080 of 8 bytes by task 18749 on cpu 1:
syslog_print kernel/printk/printk.c:1491 [inline]
do_syslog+0x1283/0x1400 kernel/printk/printk.c:1615
__do_sys_syslog kernel/printk/printk.c:1703 [inline]
__se_sys_syslog kernel/printk/printk.c:1701 [inline]
__x64_sys_syslog+0x3f/0x50 kernel/printk/printk.c:1701
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
read to 0xffffffff882f5080 of 8 bytes by task 7996 on cpu 0:
do_syslog+0xe07/0x1400 kernel/printk/printk.c:1611
kmsg_read+0x7a/0xa0 fs/proc/kmsg.c:40
pde_read fs/proc/inode.c:321 [inline]
proc_reg_read+0xe1/0x1b0 fs/proc/inode.c:331
vfs_read+0x154/0x5c0 fs/read_write.c:494
ksys_read+0xce/0x180 fs/read_write.c:634
__do_sys_read fs/read_write.c:644 [inline]
__se_sys_read fs/read_write.c:642 [inline]
__x64_sys_read+0x3e/0x50 fs/read_write.c:642
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 7996 Comm: in:imklog Not tainted 5.10.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================
---
This report 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
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.