[moderation] [fs?] [mm?] KCSAN: data-race in __filemap_add_folio / invalidate_bdev (7)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: aaf20f870da0 Merge tag 'rpmsg-v6.13' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=126843c0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=91c30f6c13debe26
dashboard link: https://syzkaller.appspot.com/bug?extid=6022f81a7134d7aaab7c
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linux-...@vger.kernel.org linu...@kvack.org wi...@infradead.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d745997c6672/disk-aaf20f87.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f5a54a8cfbd3/vmlinux-aaf20f87.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e33c52a6783f/bzImage-aaf20f87.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6022f8...@syzkaller.appspotmail.com

loop4: detected capacity change from 0 to 512
EXT4-fs: Mount option(s) incompatible with ext3
==================================================================
BUG: KCSAN: data-race in __filemap_add_folio / invalidate_bdev

read-write to 0xffff888100630570 of 8 bytes by task 3313 on cpu 0:
__filemap_add_folio+0x430/0x6f0 mm/filemap.c:919
filemap_add_folio+0x9c/0x1b0 mm/filemap.c:971
page_cache_ra_unbounded+0x177/0x310 mm/readahead.c:273
do_page_cache_ra mm/readahead.c:325 [inline]
force_page_cache_ra mm/readahead.c:354 [inline]
page_cache_sync_ra+0x252/0x670 mm/readahead.c:567
page_cache_sync_readahead include/linux/pagemap.h:1397 [inline]
filemap_get_pages+0x2c1/0x10e0 mm/filemap.c:2546
filemap_read+0x221/0x6a0 mm/filemap.c:2646
blkdev_read_iter+0x20e/0x2c0 block/fops.c:767
new_sync_read fs/read_write.c:484 [inline]
vfs_read+0x5dc/0x700 fs/read_write.c:565
ksys_read+0xe8/0x1b0 fs/read_write.c:708
__do_sys_read fs/read_write.c:717 [inline]
__se_sys_read fs/read_write.c:715 [inline]
__x64_sys_read+0x42/0x50 fs/read_write.c:715
x64_sys_call+0x2874/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:1
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888100630570 of 8 bytes by task 32387 on cpu 1:
invalidate_bdev+0x25/0x70 block/bdev.c:99
__ext4_fill_super fs/ext4/super.c:5708 [inline]
ext4_fill_super+0x6f3/0x3a10 fs/ext4/super.c:5733
get_tree_bdev_flags+0x29f/0x310 fs/super.c:1636
get_tree_bdev+0x1f/0x30 fs/super.c:1659
ext4_get_tree+0x1c/0x30 fs/ext4/super.c:5765
vfs_get_tree+0x56/0x1e0 fs/super.c:1814
do_new_mount+0x227/0x690 fs/namespace.c:3507
path_mount+0x49b/0xb30 fs/namespace.c:3834
do_mount fs/namespace.c:3847 [inline]
__do_sys_mount fs/namespace.c:4057 [inline]
__se_sys_mount+0x27c/0x2d0 fs/namespace.c:4034
__x64_sys_mount+0x67/0x80 fs/namespace.c:4034
x64_sys_call+0x2c84/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:166
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x0000000000000001 -> 0x0000000000000002

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 32387 Comm: syz.4.9538 Not tainted 6.12.0-syzkaller-10296-gaaf20f870da0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
==================================================================
loop4: detected capacity change from 0 to 512
loop4: detected capacity change from 0 to 2048
SELinux: security_context_str_to_sid (user_u) failed with errno=-22
loop4: detected capacity change from 0 to 512
EXT4-fs: Ignoring removed orlov option
EXT4-fs: Journaled quota options ignored when QUOTA feature is enabled
EXT4-fs (loop4): orphan cleanup on readonly fs
EXT4-fs error (device loop4): ext4_validate_block_bitmap:441: comm syz.4.9538: bg 0: block 248: padding at end of block bitmap is not set
EXT4-fs error (device loop4): ext4_acquire_dquot:6938: comm syz.4.9538: Failed to acquire dquot type 1
EXT4-fs (loop4): 1 truncate cleaned up


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.