Hello,
syzbot found the following issue on:
HEAD commit: e87297fa Merge tag 'drm-fixes-2020-12-04' of git://anongit..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=1732be75500000
kernel config:
https://syzkaller.appspot.com/x/.config?x=c949fed53798f819
dashboard link:
https://syzkaller.appspot.com/bug?extid=7ef7bc81239e25ce9e3d
compiler: clang version 12.0.0 (
https://github.com/llvm/llvm-project.git 913f6005669cfb590c99865a90bc51ed0983d09d)
CC: [
ak...@linux-foundation.org hu...@google.com linux-...@vger.kernel.org linu...@kvack.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+7ef7bc...@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in __percpu_counter_compare / percpu_counter_add_batch
read-write to 0xffff888100049490 of 8 bytes by task 14285 on cpu 1:
percpu_counter_add_batch+0x9b/0x100 lib/percpu_counter.c:91
percpu_counter_add include/linux/percpu_counter.h:56 [inline]
shmem_inode_acct_block mm/shmem.c:228 [inline]
shmem_alloc_and_acct_page+0x1a5/0x650 mm/shmem.c:1584
shmem_getpage_gfp+0x6b3/0x1960 mm/shmem.c:1893
shmem_getpage mm/shmem.c:155 [inline]
shmem_write_begin+0x80/0x100 mm/shmem.c:2533
generic_perform_write+0x196/0x3a0 mm/filemap.c:3329
__generic_file_write_iter+0x15c/0x330 mm/filemap.c:3458
generic_file_write_iter+0x75/0x130 mm/filemap.c:3490
call_write_iter include/linux/fs.h:1903 [inline]
new_sync_write fs/read_write.c:518 [inline]
vfs_write+0x6d4/0x7c0 fs/read_write.c:605
ksys_write+0xce/0x180 fs/read_write.c:658
__do_sys_write fs/read_write.c:670 [inline]
__se_sys_write fs/read_write.c:667 [inline]
__x64_sys_write+0x3e/0x50 fs/read_write.c:667
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
read to 0xffff888100049490 of 8 bytes by task 14262 on cpu 0:
percpu_counter_read include/linux/percpu_counter.h:72 [inline]
__percpu_counter_compare+0x28/0x1c0 lib/percpu_counter.c:225
percpu_counter_compare include/linux/percpu_counter.h:51 [inline]
shmem_inode_acct_block mm/shmem.c:225 [inline]
shmem_alloc_and_acct_page+0x12c/0x650 mm/shmem.c:1584
shmem_getpage_gfp+0x6b3/0x1960 mm/shmem.c:1893
shmem_getpage mm/shmem.c:155 [inline]
shmem_write_begin+0x80/0x100 mm/shmem.c:2533
generic_perform_write+0x196/0x3a0 mm/filemap.c:3329
__generic_file_write_iter+0x15c/0x330 mm/filemap.c:3458
generic_file_write_iter+0x75/0x130 mm/filemap.c:3490
call_write_iter include/linux/fs.h:1903 [inline]
new_sync_write fs/read_write.c:518 [inline]
vfs_write+0x6d4/0x7c0 fs/read_write.c:605
ksys_write+0xce/0x180 fs/read_write.c:658
__do_sys_write fs/read_write.c:670 [inline]
__se_sys_write fs/read_write.c:667 [inline]
__x64_sys_write+0x3e/0x50 fs/read_write.c:667
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: 14262 Comm: syz-executor.5 Not tainted 5.10.0-rc6-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.