syzbot


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

Status: auto-obsoleted due to no activity on 2023/11/20 11:49
Subsystems: ext4
[Documentation on labels]
First crash: 386d, last: 358d
Similar bugs (10)
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 727d 727d 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 532d 544d 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 (9) fs 1 263d 263d 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 36d 36d 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 422d 422d 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 179d 179d 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 771d 978d 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 313d 302d 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 1050d 1208d 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 (4) ext4 3 637d 688d 0/28 auto-obsoleted due to no activity on 2023/03/11 22:09

Sample crash report:
loop0: detected capacity change from 0 to 512
==================================================================
BUG: KCSAN: data-race in has_bh_in_lru / invalidate_bh_lrus_cpu

write to 0xffff888237d2a448 of 8 bytes by task 12201 on cpu 1:
 __invalidate_bh_lrus fs/buffer.c:1487 [inline]
 invalidate_bh_lrus_cpu+0x82/0xb0 fs/buffer.c:1532
 lru_add_and_bh_lrus_drain mm/swap.c:768 [inline]
 lru_add_drain_per_cpu+0x70/0x90 mm/swap.c:787
 process_one_work kernel/workqueue.c:2630 [inline]
 process_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2703
 worker_thread+0x525/0x730 kernel/workqueue.c:2784
 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:304

read to 0xffff888237d2a448 of 8 bytes by task 19712 on cpu 0:
 has_bh_in_lru+0x35/0x1e0 fs/buffer.c:1509
 smp_call_function_many_cond+0x2e4/0xc20 kernel/smp.c:797
 on_each_cpu_cond_mask+0x3c/0x80 kernel/smp.c:1012
 on_each_cpu_cond include/linux/smp.h:105 [inline]
 invalidate_bh_lrus+0x2a/0x30 fs/buffer.c:1518
 kill_bdev block/bdev.c:75 [inline]
 set_blocksize+0x260/0x290 block/bdev.c:152
 sb_set_blocksize+0x2d/0xb0 block/bdev.c:161
 ext4_load_super fs/ext4/super.c:5099 [inline]
 __ext4_fill_super fs/ext4/super.c:5227 [inline]
 ext4_fill_super+0xa8e/0x3940 fs/ext4/super.c:5703
 get_tree_bdev+0x272/0x300 fs/super.c:1577
 ext4_get_tree+0x1c/0x20 fs/ext4/super.c:5735
 vfs_get_tree+0x51/0x1b0 fs/super.c:1750
 do_new_mount+0x203/0x660 fs/namespace.c:3335
 path_mount+0x496/0xb30 fs/namespace.c:3662
 do_mount fs/namespace.c:3675 [inline]
 __do_sys_mount fs/namespace.c:3884 [inline]
 __se_sys_mount+0x27f/0x2d0 fs/namespace.c:3861
 __x64_sys_mount+0x67/0x80 fs/namespace.c:3861
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

value changed: 0xffff88813ccb3138 -> 0x0000000000000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 19712 Comm: syz-executor.0 Not tainted 6.6.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
==================================================================
EXT4-fs (loop0): feature flags set on rev 0 fs, running e2fsck is recommended
EXT4-fs (loop0): couldn't mount as ext3 due to feature incompatibilities

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/10/16 11:45 upstream 58720809f527 f757a323 .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/10/12 04:00 upstream 8182d7a3f1b8 83165b57 .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/09/19 01:29 upstream 2cf0f7156238 0b6a67ac .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.