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: 233d, last: 9h30m
Cause bisection: failed (error log, bisect log)
  
Discussions (1)
Title Replies (including bot) Last reply
[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 19d 192d 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 10d 186d 0/3 upstream: reported C repro on 2023/06/03 22:53
Last patch testing requests (3)
Created Duration User Patch Repo Result
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 = 4
ERROR: (device loop0): jfs_readdir: JFS:Dtree error: ino = 2, bn=0, index = 5
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:296
Write of size 4 at addr 0000000b00000000 by task syz-executor389/5033

CPU: 1 PID: 5033 Comm: syz-executor389 Not tainted 6.6.0-rc2-syzkaller-00027-g5d2f53532ecc #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/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+0x175/0x1b0 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:296
 destroy_inode fs/inode.c:307 [inline]
 evict+0x51b/0x620 fs/inode.c:679
 dispose_list fs/inode.c:697 [inline]
 evict_inodes+0x5f8/0x690 fs/inode.c:747
 generic_shutdown_super+0x9d/0x2c0 fs/super.c:672
 kill_block_super+0x41/0x70 fs/super.c:1646
 deactivate_locked_super+0xa4/0x110 fs/super.c:481
 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1254
 task_work_run+0x24a/0x300 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0xa2c/0x2650 kernel/exit.c:874
 do_group_exit+0x206/0x2c0 kernel/exit.c:1024
 __do_sys_exit_group kernel/exit.c:1035 [inline]
 __se_sys_exit_group kernel/exit.c:1033 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1033
 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
RIP: 0033:0x7f64296c07c9
Code: Unable to access opcode bytes at 0x7f64296c079f.
RSP: 002b:00007ffd3b43cc08 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f64296c07c9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007f64297412d0 R08: ffffffffffffffb8 R09: 00007ffd3b43cce0
R10: 00007ffd3b43cce0 R11: 0000000000000246 R12: 00007f64297412d0
R13: 0000000000000000 R14: 00007f6429742040 R15: 00007f642968ed10
 </TASK>
==================================================================

Crashes (64):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
2023/12/07 02:08 upstream bee0e7762ad2 e3299f55 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/12/05 12:12 upstream bee0e7762ad2 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/12/05 01:10 upstream bee0e7762ad2 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/12/04 20:56 upstream 33cc938e65a9 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/12/04 05:59 upstream 33cc938e65a9 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/12/03 23:58 upstream 33cc938e65a9 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/12/02 22:21 upstream 815fb87b7530 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/11/27 03:16 upstream d2da77f431ac 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/11/27 00:17 upstream d2da77f431ac 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/11/04 21:09 upstream 90b0c2b2edd1 500bfdc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/11/03 18:34 upstream 8f6f76a6a29f c4ac074c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/11/02 19:07 upstream babe393974de 69904c9f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/10/26 01:46 upstream 611da07b89fd 72e794c4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/10/16 01:02 upstream fbe1bf1e5ff1 f757a323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/10/12 19:04 upstream 401644852d0b 1b231e3c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/10/04 06:55 upstream 5e62ed3b1c8a 65faba36 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/10/03 17:05 upstream ce36c8b14987 65faba36 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/10/02 19:56 upstream 8a749fd1a872 50b20e75 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/09/28 05:51 upstream 633b47cb009d c2ab1e5d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/09/21 19:21 upstream 42dc814987c1 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/09/17 00:34 upstream f0b0d403eabb 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/09/06 04:27 upstream 7733171926cc 0b6286dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/09/01 13:43 upstream 99d99825fc07 696ea0d2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/08/31 06:32 upstream ef2a0b7cdbc5 84803932 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/08/22 21:33 upstream 53663f4103ff b81ca3f6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/08/17 08:26 upstream 4853c74bd7ab 74b106b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/08/14 12:08 upstream 2ccdd1b13c59 39990d51 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/08/12 10:31 upstream f8de32cc060b 39990d51 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/08/12 03:51 upstream 9106536c1aa3 39990d51 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/07/31 17:21 upstream 5d0c230f1de8 2a0d0f29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/07/18 11:06 upstream fdf0eaf11452 20f8b3c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/06/24 20:32 upstream a92b7d26c743 79782afc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/06/22 19:28 upstream dad9774deaf1 79782afc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/06/18 12:43 upstream 1b29d271614a f3921d4d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/06/16 23:01 upstream 40f71e7cd3c6 f3921d4d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/06/13 21:50 upstream 15adb51c04cc d2ee9228 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/06/08 16:00 upstream 5f63595ebd82 058b3a5a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/06/03 07:34 upstream 4ecd704a4c51 a4ae4f42 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/31 15:31 upstream afead42fdfca 09898419 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/30 21:20 upstream 8b817fded42d df37c7f1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/30 15:23 upstream 8b817fded42d cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/30 04:59 upstream 8b817fded42d cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/27 19:24 upstream 49572d536129 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/27 05:22 upstream 0d85b27b0cc6 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/27 03:20 upstream 0d85b27b0cc6 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/27 02:40 upstream 0d85b27b0cc6 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/25 17:51 upstream 933174ae28ba 0513b3e6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/25 14:32 upstream 933174ae28ba 0513b3e6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/22 15:00 upstream 44c026a73be8 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/22 01:29 upstream e2065b8c1b01 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/13 15:13 upstream 9a48d6046722 2b9ba477 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/08 14:40 upstream ac9a78681b92 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/07 17:55 upstream fc4354c6e5c2 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/05/04 08:54 upstream fa31fc82fb77 5b7ff9dd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/04/25 09:47 upstream 1a0beef98b58 65320f8e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/04/24 16:58 upstream 457391b03803 fdc18293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/04/24 10:12 upstream 457391b03803 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/04/23 18:50 upstream 622322f53c6d 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2023/04/22 15:12 upstream 8e41e0a57566 2b32bd34 .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.