Hello,
syzbot found the following issue on:
HEAD commit: 99613159ad74 Merge tag 'dmaengine-5.17-rc1' of git://git.k..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=1720cfa7b00000
kernel config:
https://syzkaller.appspot.com/x/.config?x=9b7e9e887db22f84
dashboard link:
https://syzkaller.appspot.com/bug?extid=e67dc043a513bfe90e09
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [
linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]
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+e67dc0...@syzkaller.appspotmail.com
==================================================================
BUG: KCSAN: data-race in generic_write_end / next_uptodate_page
write to 0xffff888133892b88 of 8 bytes by task 12387 on cpu 1:
i_size_write include/linux/fs.h:914 [inline]
generic_write_end+0x96/0x180 fs/buffer.c:2187
ext4_da_write_end+0x448/0x510 fs/ext4/inode.c:3042
generic_perform_write+0x261/0x400 mm/filemap.c:3698
ext4_buffered_write_iter+0x19d/0x290 fs/ext4/file.c:268
ext4_file_write_iter+0x227/0xda0
call_write_iter include/linux/fs.h:2086 [inline]
new_sync_write fs/read_write.c:503 [inline]
vfs_write+0x7f5/0x950 fs/read_write.c:590
ksys_write+0xd9/0x190 fs/read_write.c:643
__do_sys_write fs/read_write.c:655 [inline]
__se_sys_write fs/read_write.c:652 [inline]
__x64_sys_write+0x3e/0x50 fs/read_write.c:652
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
read to 0xffff888133892b88 of 8 bytes by task 12389 on cpu 0:
i_size_read include/linux/fs.h:892 [inline]
next_uptodate_page+0x279/0x540 mm/filemap.c:3212
next_map_page mm/filemap.c:3237 [inline]
filemap_map_pages+0x7b6/0x8d0 mm/filemap.c:3304
do_fault_around mm/memory.c:4166 [inline]
do_read_fault mm/memory.c:4181 [inline]
do_fault mm/memory.c:4316 [inline]
handle_pte_fault mm/memory.c:4574 [inline]
__handle_mm_fault mm/memory.c:4709 [inline]
handle_mm_fault+0xaf7/0x1590 mm/memory.c:4807
faultin_page mm/gup.c:944 [inline]
__get_user_pages+0x388/0xc80 mm/gup.c:1165
populate_vma_page_range mm/gup.c:1497 [inline]
__mm_populate+0x24d/0x370 mm/gup.c:1606
mm_populate include/linux/mm.h:2675 [inline]
vm_mmap_pgoff+0x160/0x1f0 mm/util.c:524
ksys_mmap_pgoff+0x265/0x320 mm/mmap.c:1630
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
value changed: 0x00000000020a4000 -> 0x00000000020a7000
Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 12389 Comm: syz-executor.5 Not tainted 5.16.0-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.