syzbot


KASAN: user-memory-access Write in __destroy_inode

Status: upstream: reported C repro on 2023/05/04 09:32
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+dcc068159182a4c31ca3@syzkaller.appspotmail.com
First crash: 345d, last: 16d
Cause bisection: failed (error log, bisect log)
  
Discussions (3)
Title Replies (including bot) Last reply
[syzbot] Monthly jfs report (Mar 2024) 0 (1) 2024/03/06 22:08
[syzbot] Monthly jfs report (Feb 2024) 0 (1) 2024/02/04 13:30
[syzbot] [jfs?] KASAN: user-memory-access Write in __destroy_inode 0 (1) 2023/05/04 09:32
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 KASAN: user-memory-access Write in __destroy_inode origin:upstream C 1 1d02h 304d 0/3 upstream: reported C repro on 2023/05/28 20:49
linux-6.1 KASAN: user-memory-access Write in __destroy_inode origin:upstream C 1 18d 298d 0/3 upstream: reported C repro on 2023/06/03 22:53
Last patch testing requests (5)
Created Duration User Patch Repo Result
2024/03/25 18:39 21m retest repro upstream error OK
2024/03/25 18:39 47m retest repro upstream error OK
2023/11/18 23:20 15m retest repro upstream report log
2023/11/18 23:20 13m retest repro upstream report log
2023/11/18 22:32 20m retest repro linux-next OK log

Sample crash report:
ERROR: (device loop0): jfs_readdir: JFS:Dtree error: ino = 2, bn=0, index = 6
ERROR: (device loop0): jfs_readdir: JFS:Dtree error: ino = 2, bn=0, index = 7
==================================================================
BUG: KASAN: user-memory-access in instrument_atomic_read_write include/linux/instrumented.h:96 [inline]
BUG: KASAN: user-memory-access in atomic_fetch_sub_release include/linux/atomic/atomic-instrumented.h:400 [inline]
BUG: KASAN: user-memory-access in __refcount_sub_and_test include/linux/refcount.h:272 [inline]
BUG: KASAN: user-memory-access in __refcount_dec_and_test include/linux/refcount.h:315 [inline]
BUG: KASAN: user-memory-access in refcount_dec_and_test include/linux/refcount.h:333 [inline]
BUG: KASAN: user-memory-access in posix_acl_release include/linux/posix_acl.h:57 [inline]
BUG: KASAN: user-memory-access in __destroy_inode+0x479/0x640 fs/inode.c:298
Write of size 4 at addr 0000000b00000000 by task syz-executor173/5059

CPU: 1 PID: 5059 Comm: syz-executor173 Not tainted 6.7.0-rc7-syzkaller-00041-gf016f7547aee #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 print_report+0xe6/0x540 mm/kasan/report.c:478
 kasan_report+0x142/0x170 mm/kasan/report.c:588
 kasan_check_range+0x27e/0x290 mm/kasan/generic.c:187
 instrument_atomic_read_write include/linux/instrumented.h:96 [inline]
 atomic_fetch_sub_release include/linux/atomic/atomic-instrumented.h:400 [inline]
 __refcount_sub_and_test include/linux/refcount.h:272 [inline]
 __refcount_dec_and_test include/linux/refcount.h:315 [inline]
 refcount_dec_and_test include/linux/refcount.h:333 [inline]
 posix_acl_release include/linux/posix_acl.h:57 [inline]
 __destroy_inode+0x479/0x640 fs/inode.c:298
 destroy_inode fs/inode.c:309 [inline]
 evict+0x51b/0x630 fs/inode.c:681
 dispose_list fs/inode.c:699 [inline]
 evict_inodes+0x5f8/0x690 fs/inode.c:749
 generic_shutdown_super+0x9d/0x2c0 fs/super.c:675
 kill_block_super+0x44/0x90 fs/super.c:1667
 deactivate_locked_super+0xc1/0x130 fs/super.c:484
 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256
 task_work_run+0x24a/0x300 kernel/task_work.c:180
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0xa2c/0x2740 kernel/exit.c:869
 do_group_exit+0x206/0x2c0 kernel/exit.c:1018
 __do_sys_exit_group kernel/exit.c:1029 [inline]
 __se_sys_exit_group kernel/exit.c:1027 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1027
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0x45/0x110 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7fd94063a7c9
Code: Unable to access opcode bytes at 0x7fd94063a79f.
RSP: 002b:00007ffdf4aaff08 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fd94063a7c9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007fd9406bb2d0 R08: ffffffffffffffb8 R09: 00007ffdf4aaffe0
R10: 00007ffdf4aaffe0 R11: 0000000000000246 R12: 00007fd9406bb2d0
R13: 0000000000000000 R14: 00007fd9406bc040 R15: 00007fd940608d20
 </TASK>
==================================================================

Crashes (148):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/12/30 13:57 upstream f016f7547aee fb427a07 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/09/20 23:55 upstream 5d2f53532ecc 0b6a67ac .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root KASAN: user-memory-access Write in __destroy_inode
2023/06/17 00:59 upstream 40f71e7cd3c6 f3921d4d .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2023/05/04 09:31 upstream fa31fc82fb77 5b7ff9dd .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/07/23 13:57 linux-next ae867bc97b71 27cbe77f .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2024/03/11 17:54 upstream e8f897f4afef 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/03/09 06:41 upstream 10d48d70e82d 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/03/08 09:18 upstream 3aaa8ce7a335 cf82cde1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/03/08 00:43 upstream 135288b73cef 2b789849 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/03/06 07:50 upstream 29cd507cbec2 f39a7eed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/03/06 06:38 upstream 29cd507cbec2 f39a7eed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/03/05 15:46 upstream 90d35da658da f39a7eed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/03/05 04:26 upstream 90d35da658da 5fc53669 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/03/04 06:05 upstream 58c806d867bf 25905f5d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/03/02 13:32 upstream 17ba56605bfd 25905f5d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/29 22:03 upstream 805d849d7c3c 352ab904 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/29 06:51 upstream e326df53af00 352ab904 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/28 21:57 upstream e326df53af00 55d6f11d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/28 14:51 upstream cf1182944c7c 55d6f11d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/28 00:29 upstream 45ec2f5f6ed3 d367cbe5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/27 09:08 upstream 45ec2f5f6ed3 05e69c83 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/26 13:35 upstream d206a76d7d27 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/26 09:06 upstream 70ff1fe626a1 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/25 19:08 upstream ab0a97cffa0b 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/25 08:02 upstream f2e367d6ad3b 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/25 05:09 upstream f2e367d6ad3b 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/25 03:43 upstream f2e367d6ad3b 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/24 15:18 upstream 603c04e27c3e 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/23 11:27 upstream ffd2cb6b718e 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/21 16:29 upstream 9fc1ccccfd8d 3af7dd65 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/19 05:23 upstream b401b621758e 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/18 02:23 upstream ced590523156 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/17 16:15 upstream c1ca10ceffbb 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/17 10:01 upstream c1ca10ceffbb 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/16 15:10 upstream 4f5e5092fdbf 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/16 14:00 upstream 4f5e5092fdbf 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/14 01:24 upstream c664e16bb1ba e66542d7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/13 09:40 upstream c664e16bb1ba 77b23aa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/11 06:52 upstream a5b6244cf87c 77b23aa1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/08 11:08 upstream 547ab8fc4cb0 6404acf9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/02 12:34 upstream 5c24e4e9e708 d61103fc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/02/02 03:51 upstream 5c24e4e9e708 d61103fc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/01/30 22:24 upstream 861c0981648f 7f400fcb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/01/29 23:54 upstream 41bccc98fb79 991a98f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/01/26 15:32 upstream ecb1b8288dc7 cc4a4020 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/01/25 02:55 upstream 443b349019f2 1e153dc8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/01/24 12:59 upstream 615d30064886 1e153dc8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/01/23 19:43 upstream 7ed2632ec7d7 1e153dc8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/01/23 15:16 upstream 5d9248eed480 1c0ecc51 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/01/22 14:22 upstream 6613476e225e 9bd8dcda .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/01/22 09:57 upstream 4fbbed787267 9bd8dcda .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/01/21 19:53 upstream 7a396820222d 9bd8dcda .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/04/17 19:14 upstream 6a8f57ae2eb0 c6ec7083 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
* Struck through repros no longer work on HEAD.