syzbot


KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru (2)
Status: moderation: reported on 2021/10/01 15:57
Reported-by: syzbot+aea2daf492f8a5b182aa@syzkaller.appspotmail.com
First crash: 421d, last: 3d07h
similar bugs (1):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru 14 841d 908d 0/22 auto-closed as invalid on 2020/04/15 20:03

Sample crash report:
loop1: detected capacity change from 0 to 2224
==================================================================
BUG: KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru

write to 0xffff888237c28438 of 8 bytes by task 10111 on cpu 0:
 __invalidate_bh_lrus fs/buffer.c:1392 [inline]
 invalidate_bh_lru+0xad/0x110 fs/buffer.c:1404
 smp_call_function_many_cond+0x4f1/0x6d0 kernel/smp.c:960
 on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1135
 on_each_cpu_cond include/linux/smp.h:105 [inline]
 invalidate_bh_lrus+0x26/0x30 fs/buffer.c:1423
 kill_bdev block/bdev.c:76 [inline]
 set_blocksize+0x242/0x270 block/bdev.c:153
 sb_set_blocksize+0x2c/0xa0 block/bdev.c:162
 isofs_fill_super+0xfc2/0x17b0 fs/isofs/inode.c:862
 mount_bdev+0x1e2/0x280 fs/super.c:1367
 isofs_mount+0x2d/0x40 fs/isofs/inode.c:1567
 legacy_get_tree+0x70/0xc0 fs/fs_context.c:610
 vfs_get_tree+0x49/0x190 fs/super.c:1497
 do_new_mount+0x200/0x650 fs/namespace.c:3040
 path_mount+0x4b1/0xb60 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount+0x281/0x2d0 fs/namespace.c:3568
 __x64_sys_mount+0x63/0x70 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888237c28438 of 8 bytes by task 10112 on cpu 1:
 has_bh_in_lru+0x31/0x1c0 fs/buffer.c:1414
 smp_call_function_many_cond+0x2a9/0x6d0 kernel/smp.c:917
 on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1135
 on_each_cpu_cond include/linux/smp.h:105 [inline]
 invalidate_bh_lrus+0x26/0x30 fs/buffer.c:1423
 kill_bdev block/bdev.c:76 [inline]
 set_blocksize+0x242/0x270 block/bdev.c:153
 sb_set_blocksize+0x2c/0xa0 block/bdev.c:162
 isofs_fill_super+0xfc2/0x17b0 fs/isofs/inode.c:862
 mount_bdev+0x1e2/0x280 fs/super.c:1367
 isofs_mount+0x2d/0x40 fs/isofs/inode.c:1567
 legacy_get_tree+0x70/0xc0 fs/fs_context.c:610
 vfs_get_tree+0x49/0x190 fs/super.c:1497
 do_new_mount+0x200/0x650 fs/namespace.c:3040
 path_mount+0x4b1/0xb60 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount+0x281/0x2d0 fs/namespace.c:3568
 __x64_sys_mount+0x63/0x70 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0xffff888169a55888 -> 0x0000000000000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 10112 Comm: syz-executor.1 Not tainted 5.18.0-syzkaller-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================

Crashes (141):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-upstream-kcsan-gce 2022/05/23 17:38 upstream 4b0986a3613c 4c7657cb .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/05/20 01:18 upstream b015dcd62b86 cb1ac2e7 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/05/14 16:50 upstream ec7f49619d8e 744a39e2 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/05/12 00:40 upstream feb9c5e19e91 beb0b407 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/05/09 23:43 upstream 9be9ed2612b5 8b277b8e .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/04/24 16:39 upstream 22da5264abf4 131df97d .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/04/21 03:00 upstream 559089e0a93d d4befee1 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/04/19 05:27 upstream b2d229d4ddb1 8bcc32a6 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/04/17 14:32 upstream 90ea17a9e27b 8bcc32a6 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/04/13 09:19 upstream a19944809fe9 faabdb86 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/04/11 22:41 upstream ce522ba9ef7e af01ee7d .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/04/10 06:45 upstream e1f700ebd6be e22c3da3 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/04/04 08:57 upstream 09bb8856d4a7 79a2a8fc .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/03/29 19:00 upstream 1930a6e739c4 6bdac766 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/03/26 06:52 upstream 52d543b5497c 89bc8608 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/03/24 21:17 upstream ed4643521e6a 89bc8608 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/03/23 12:41 upstream 3bf03b9a0839 5ff41e94 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/03/19 01:55 upstream 551acdc3c3d2 e2d91b1d .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/03/12 10:56 upstream 68453767131a 9e8eaa75 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/03/08 09:47 upstream ea4424be1688 7bdd8b2c .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/02/28 08:22 upstream 52a025546731 45a13a73 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/02/22 13:45 upstream 038101e6b2cd 6e821dbf .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/02/21 19:18 upstream cfb92440ee71 3cd800e4 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/02/14 23:45 upstream d567f5db412e 8b9ca619 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/02/11 10:42 upstream f1baf68e1383 0b33604d .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/02/08 20:13 upstream 555f3d7be91a 0b33604d .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/02/05 21:53 upstream 0457e5153e0e a7dab638 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/01/29 21:42 upstream f8c7e4ede46f 495e00c5 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/01/27 22:27 upstream 626b2dda7651 64a8e201 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/01/23 06:07 upstream 1c52283265a4 214351e1 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/01/22 10:30 upstream 0809edbae347 214351e1 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/01/19 18:04 upstream e9f5cbc0c851 0620189b .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/01/17 09:58 upstream 79e06c4c4950 723cfaf0 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/01/16 01:54 upstream a33f5c380c4b 723cfaf0 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/01/15 16:31 upstream 112450df61b7 723cfaf0 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/01/07 12:16 upstream b2b436ec0205 6acc789a .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/01/06 14:17 upstream 75acfdb6fd92 6acc789a .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/01/05 14:14 upstream c9e6606c7fe9 0a2584dd .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2022/01/02 12:01 upstream 278218f6778b e1768e9c .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2021/12/29 18:09 upstream e7c124bd0463 6cc879d4 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2021/12/29 01:36 upstream ecf71de775a0 76c8cf06 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2021/12/27 08:06 upstream fc74e0a40e4f e4f103c4 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2021/10/01 05:00 upstream 4de593fb965f 1d849ab4 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2021/09/27 15:43 upstream 5816b3e6577e 78494d16 .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru
ci2-upstream-kcsan-gce 2021/04/01 00:50 upstream d19cc4bfbff1 6a81331a .config log report info KCSAN: data-race in has_bh_in_lru / invalidate_bh_lru