[moderation] [block?] KCSAN: data-race in delete_from_page_cache_batch / nr_blockdev_pages (10)

2 views
Skip to first unread message

syzbot

unread,
Mar 4, 2024, 7:16:29 AMMar 4
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 90d35da658da Linux 6.8-rc7
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12fc55a2180000
kernel config: https://syzkaller.appspot.com/x/.config?x=f10ff55d327ef698
dashboard link: https://syzkaller.appspot.com/bug?extid=905741ed580a4d9ed64c
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ax...@kernel.dk linux...@vger.kernel.org linux-...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/db68fe219e77/disk-90d35da6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/feb8e6632739/vmlinux-90d35da6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0c6e98b6523c/bzImage-90d35da6.xz

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

==================================================================
BUG: KCSAN: data-race in delete_from_page_cache_batch / nr_blockdev_pages

read-write to 0xffff8881006311f0 of 8 bytes by task 3095 on cpu 1:
page_cache_delete_batch mm/filemap.c:315 [inline]
delete_from_page_cache_batch+0x515/0x710 mm/filemap.c:334
truncate_inode_pages_range+0x1bd/0x6a0 mm/truncate.c:359
truncate_inode_pages+0x24/0x30 mm/truncate.c:439
kill_bdev block/bdev.c:79 [inline]
blkdev_flush_mapping+0xc2/0x1c0 block/bdev.c:638
blkdev_put_whole block/bdev.c:669 [inline]
bdev_release+0x3f6/0x540 block/bdev.c:985
kill_block_super+0x54/0x60 fs/super.c:1678
deactivate_locked_super+0x7a/0x1c0 fs/super.c:472
deactivate_super+0x9b/0xb0 fs/super.c:505
cleanup_mnt+0x272/0x2e0 fs/namespace.c:1267
__cleanup_mnt+0x19/0x20 fs/namespace.c:1274
task_work_run+0x135/0x1a0 kernel/task_work.c:180
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:108 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:201 [inline]
syscall_exit_to_user_mode+0xbd/0x120 kernel/entry/common.c:212
do_syscall_64+0xda/0x1d0 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff8881006311f0 of 8 bytes by task 904 on cpu 0:
nr_blockdev_pages+0x7c/0xd0 block/bdev.c:449
si_meminfo+0x87/0xd0 mm/show_mem.c:80
update_defense_level+0x46/0x600 net/netfilter/ipvs/ip_vs_ctl.c:101
defense_work_handler+0x1f/0x80 net/netfilter/ipvs/ip_vs_ctl.c:235
process_one_work kernel/workqueue.c:2633 [inline]
process_scheduled_works+0x5b8/0xa40 kernel/workqueue.c:2706
worker_thread+0x525/0x730 kernel/workqueue.c:2787
kthread+0x1d7/0x210 kernel/kthread.c:388
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:243

value changed: 0x0000000000000027 -> 0x0000000000000018

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 904 Comm: kworker/0:2 Not tainted 6.8.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: events_long defense_work_handler
==================================================================


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

unread,
Apr 8, 2024, 8:17:14 AMApr 8
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages