syzbot


KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu (4)

Status: auto-obsoleted due to no activity on 2023/03/11 22:09
Subsystems: ext4
[Documentation on labels]
First crash: 745d, last: 694d
Similar bugs (11)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu (3) fs 1 783d 783d 0/28 auto-obsoleted due to no activity on 2022/11/16 21:51
upstream KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu (5) fs 2 589d 601d 0/28 auto-obsoleted due to no activity on 2023/05/30 05:48
upstream KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu (7) ext4 3 415d 442d 0/28 auto-obsoleted due to no activity on 2023/11/20 11:49
upstream KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu (9) fs 1 320d 320d 0/28 auto-obsoleted due to no activity on 2024/02/23 17:16
upstream KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu (11) exfat 1 93d 93d 0/28 auto-obsoleted due to no activity on 2024/10/07 09:54
upstream KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu (6) ext4 1 479d 479d 0/28 auto-obsoleted due to no activity on 2023/09/17 01:43
upstream KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu (10) fs 1 235d 235d 0/28 auto-obsoleted due to no activity on 2024/05/17 23:40
upstream KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu (2) fs 14 828d 1034d 0/28 auto-closed as invalid on 2022/10/03 06:12
upstream KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu (8) ext4 1 370d 358d 0/28 auto-obsoleted due to no activity on 2024/01/04 10:47
upstream KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu ext4 137 1107d 1265d 0/28 auto-closed as invalid on 2021/12/28 13:59
upstream KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu (12) fs 1 49d 49d 0/28 auto-obsoleted due to no activity on 2024/11/20 10:12

Sample crash report:
==================================================================
BUG: KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu

write to 0xffff888237d286b8 of 8 bytes by task 3219 on cpu 1:
 __invalidate_bh_lrus fs/buffer.c:1381 [inline]
 invalidate_bh_lrus_cpu+0xad/0xe0 fs/buffer.c:1426
 lru_add_and_bh_lrus_drain mm/swap.c:802 [inline]
 lru_add_drain_per_cpu+0x4e/0x70 mm/swap.c:821
 process_one_work+0x3d3/0x720 kernel/workqueue.c:2289
 process_scheduled_works kernel/workqueue.c:2352 [inline]
 worker_thread+0x78f/0xa70 kernel/workqueue.c:2441
 kthread+0x1a9/0x1e0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308

read to 0xffff888237d286b8 of 8 bytes by task 3128 on cpu 0:
 has_bh_in_lru+0x31/0x1c0 fs/buffer.c:1403
 smp_call_function_many_cond+0x2e3/0x650 kernel/smp.c:935
 on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1155
 on_each_cpu_cond include/linux/smp.h:105 [inline]
 invalidate_bh_lrus+0x26/0x30 fs/buffer.c:1412
 invalidate_bdev+0x51/0x80 block/bdev.c:85
 ext4_put_super+0x510/0x810 fs/ext4/super.c:1273
 generic_shutdown_super+0xd5/0x240 fs/super.c:492
 kill_block_super+0x4a/0x90 fs/super.c:1386
 deactivate_locked_super+0x6a/0xb0 fs/super.c:332
 deactivate_super+0x85/0x90 fs/super.c:363
 cleanup_mnt+0x267/0x2d0 fs/namespace.c:1291
 __cleanup_mnt+0x15/0x20 fs/namespace.c:1298
 task_work_run+0xde/0x110 kernel/task_work.c:179
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop+0x124/0x130 kernel/entry/common.c:171
 exit_to_user_mode_prepare kernel/entry/common.c:203 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
 syscall_exit_to_user_mode+0x6a/0x90 kernel/entry/common.c:296
 do_syscall_64+0x37/0x70 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

value changed: 0xffff88810b221068 -> 0x0000000000000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 3128 Comm: syz-executor.2 Not tainted 6.2.0-rc3-syzkaller-00008-g1fe4fd6f5cad-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
==================================================================
EXT4-fs (loop2): unmounting filesystem 00000000-0000-0000-0000-000000000000.
EXT4-fs (loop2): unmounting filesystem 00000000-0000-0000-0000-000000000000.

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/10 02:20 upstream 1fe4fd6f5cad 48bc529a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu
2023/01/07 06:13 upstream 1f5abbd77e2c 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu
2022/11/20 02:21 upstream fe24a97cf254 5bb70014 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu
* Struck through repros no longer work on HEAD.