syzbot


KASAN: user-memory-access Write in __destroy_inode

Status: auto-obsoleted due to no activity on 2026/03/04 16:01
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+dcc068159182a4c31ca3@syzkaller.appspotmail.com
First crash: 1057d, last: 92d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: fixed by (bisect log) :
commit dca3aa666fbd71118905d88bb1c353881002b647
Author: Mateusz Guzik <mjguzik@gmail.com>
Date: Sun Nov 9 12:19:31 2025 +0000

  fs: move inode fields used during fast path lookup closer together

  
Discussions (22)
Title Replies (including bot) Last reply
Re: [syzbot] [jfs?] KASAN: user-memory-access Write in __destroy_inode 1 (1) 2026/01/07 15:05
[syzbot] [jfs?] KASAN: user-memory-access Write in __destroy_inode 0 (3) 2026/01/07 14:57
[syzbot] Monthly jfs report (Nov 2025) 0 (1) 2025/11/25 08:46
[syzbot] Monthly jfs report (Oct 2025) 0 (1) 2025/10/24 18:48
[syzbot] Monthly jfs report (Sep 2025) 0 (1) 2025/09/23 06:49
[syzbot] Monthly jfs report (Aug 2025) 0 (1) 2025/08/23 16:31
[syzbot] Monthly jfs report (Jul 2025) 0 (1) 2025/07/22 12:43
[syzbot] Monthly jfs report (Jun 2025) 0 (1) 2025/06/23 07:31
[syzbot] Monthly jfs report (May 2025) 0 (1) 2025/05/21 14:56
[syzbot] Monthly jfs report (Apr 2025) 0 (1) 2025/04/22 10:11
[syzbot] Monthly jfs report (Mar 2025) 0 (1) 2025/03/19 21:29
[syzbot] Monthly jfs report (Feb 2025) 0 (1) 2025/02/16 21:54
[syzbot] Monthly jfs report (Jan 2025) 0 (1) 2025/01/16 10:11
[syzbot] Monthly jfs report (Dec 2024) 0 (1) 2024/12/16 09:45
[syzbot] Monthly jfs report (Nov 2024) 0 (1) 2024/11/15 10:49
[syzbot] Monthly jfs report (Oct 2024) 0 (1) 2024/10/14 19:37
[syzbot] Monthly jfs report (Sep 2024) 0 (1) 2024/09/13 10:03
[syzbot] Monthly jfs report (Aug 2024) 0 (1) 2024/08/13 08:52
[syzbot] Monthly jfs report (Jul 2024) 0 (1) 2024/07/12 12:56
[syzbot] Monthly jfs report (Jun 2024) 0 (1) 2024/06/11 08:27
[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
Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 KASAN: user-memory-access Write in __destroy_inode origin:upstream 21 C error 254 8d21h 1016d 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 missing-backport 21 C error 356 50d 1010d 0/3 upstream: reported C repro on 2023/06/03 22:53
Last patch testing requests (11)
Created Duration User Patch Repo Result
2026/03/04 15:42 30m retest repro upstream OK log
2026/03/04 15:39 21m retest repro upstream OK log
2025/12/24 18:31 19m retest repro upstream OK log
2025/12/24 18:31 23m retest repro upstream OK log
2025/12/24 18:31 40m retest repro upstream OK log
2025/12/24 18:31 19m retest repro upstream OK log
2025/12/24 18:31 21m retest repro upstream OK log
2025/12/24 12:25 23m retest repro upstream report log
2025/12/24 12:25 24m retest repro upstream OK log
2025/12/24 12:25 19m retest repro upstream OK log
2025/09/24 19:11 30m dmantipov@yandex.ru patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git cec1e6e5d1ab33403b809f79cd20d6aff124ccfe OK log

Sample crash report:
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+0x3bf/0x740 fs/inode.c:297
Write of size 4 at addr 0000000b00000000 by task syz-executor123/5036

CPU: 0 PID: 5036 Comm: syz-executor123 Not tainted 6.5.0-rc2-next-20230721-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
 kasan_report+0xda/0x110 mm/kasan/report.c:588
 check_region_inline mm/kasan/generic.c:181 [inline]
 kasan_check_range+0xef/0x190 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+0x3bf/0x740 fs/inode.c:297
 destroy_inode+0x91/0x1b0 fs/inode.c:308
 dispose_list+0x117/0x1e0 fs/inode.c:698
 evict_inodes+0x34f/0x450 fs/inode.c:748
 generic_shutdown_super+0xaf/0x480 fs/super.c:478
 kill_block_super+0x64/0xb0 fs/super.c:1417
 deactivate_locked_super+0x9a/0x170 fs/super.c:330
 deactivate_super+0xde/0x100 fs/super.c:361
 cleanup_mnt+0x222/0x3d0 fs/namespace.c:1254
 task_work_run+0x14d/0x240 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0xa99/0x2a20 kernel/exit.c:874
 do_group_exit+0xd4/0x2a0 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+0x3e/0x50 kernel/exit.c:1033
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fbaa7ba57c9
Code: Unable to access opcode bytes at 0x7fbaa7ba579f.
RSP: 002b:00007ffdf9215b98 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fbaa7ba57c9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007fbaa7c262d0 R08: ffffffffffffffb8 R09: 00007ffdf9215c70
R10: 00007ffdf9215c70 R11: 0000000000000246 R12: 00007fbaa7c262d0
R13: 0000000000000000 R14: 00007fbaa7c27040 R15: 00007fbaa7b73d10
 </TASK>
==================================================================

Crashes (3472):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
2025/12/02 06:59 upstream 1d18101a644e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/29 16:24 upstream 19eef1d98eed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/26 13:23 upstream 30f09200cc4a 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/25 08:58 upstream ac3fd01e4c1e 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/24 01:36 upstream d0e88704d96c 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/23 18:11 upstream d13f3ac64efb 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/22 11:56 upstream 2eba5e05d9bc 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/21 02:01 upstream 8e621c9a3375 2cc4c24a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/19 00:02 upstream 5bebe8de1926 ef766cd7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/18 14:27 upstream e7c375b18160 ef766cd7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/16 20:25 upstream 7254a2b52279 f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/16 07:10 upstream f824272b6e3f f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/12 02:32 upstream 24172e0d7990 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2025/11/11 15:28 upstream 4427259cc7f7 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/11 13:32 upstream 4427259cc7f7 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/11 13:21 upstream 4427259cc7f7 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/10 13:51 upstream e9a6fb0bcdd7 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/08 19:53 upstream e811c33b1f13 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/08 19:53 upstream e811c33b1f13 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/06 06:03 upstream 1c353dc8d962 a6c9c731 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/04 17:23 upstream c9cfc122f037 686bf657 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/03 07:32 upstream 6146a0f1dfae 2c50b6a9 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2025/11/03 07:22 upstream 6146a0f1dfae 2c50b6a9 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/03 06:14 upstream 6146a0f1dfae 2c50b6a9 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/03 05:00 upstream 6146a0f1dfae 2c50b6a9 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/11/03 03:47 upstream 6146a0f1dfae 2c50b6a9 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/10/31 06:57 upstream e53642b87a4f 2c50b6a9 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2025/10/29 10:42 upstream 8eefed8f65cc fd2207e7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/10/29 03:39 upstream 8eefed8f65cc fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/10/26 19:56 upstream dbfc6422a34d c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/10/25 14:54 upstream 566771afc7a8 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2025/10/21 16:38 upstream 6548d364a3e8 9832ed61 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/10/20 04:19 upstream d9043c79ba68 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/10/12 23:24 upstream 67029a49db6c ff1712fe .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2025/10/06 07:58 upstream 7a405dbb0f03 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/10/05 17:54 upstream 6093a688a07d 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/09/28 22:40 upstream 8f9736633f8c 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/09/26 11:50 upstream 4ff71af020ae 0abd0691 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2025/09/24 06:35 upstream cec1e6e5d1ab 0abd0691 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2025/09/22 07:17 upstream 2d5bd41a4505 67c37560 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/09/17 18:26 upstream 5aca7966d2a7 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2025/09/07 09:06 upstream b236920731dd d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/08/24 13:27 upstream 8d245acc1e88 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/08/20 15:54 upstream b19a97d57c15 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/08/20 15:48 upstream b19a97d57c15 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/08/18 06:28 upstream 8d561baae505 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/08/17 14:32 upstream 99bade344cfa 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/08/07 23:27 upstream 6e64f4580381 04cffc22 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2025/07/08 09:15 upstream d7b8f8e20813 4f67c4ae .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/07/08 07:30 upstream d7b8f8e20813 4f67c4ae .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/07/08 05:45 upstream d7b8f8e20813 4f67c4ae .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/07/08 04:01 upstream d7b8f8e20813 4f67c4ae .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/07/08 01:33 upstream d7b8f8e20813 4f67c4ae .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/01/15 13:37 upstream 619f0b6fad52 7315a7cf .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/01/10 13:35 upstream 643e2e259c2b 67d7ec0a .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2025/01/03 23:02 upstream 0bc21e701a6f f3558dbf .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/12/28 18:31 upstream fd0584d220fe d3ccff63 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/12/28 16:24 upstream fd0584d220fe d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root KASAN: user-memory-access Write in __destroy_inode
2024/10/31 11:13 upstream 4236f913808c 96eb609f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/10/27 04:27 upstream 850925a8133c 65e8686b .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-badwrites-root KASAN: user-memory-access Write in __destroy_inode
2024/10/08 09:20 upstream 87d6aab2389e 402f1df0 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/10/03 18:17 upstream 7ec462100ef9 d7906eff .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/06/19 18:59 upstream 2ccbdf43d5e7 41b7e219 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/06/19 17:31 upstream 2ccbdf43d5e7 41b7e219 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/06/19 15:57 upstream 2ccbdf43d5e7 41b7e219 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: user-memory-access Write in __destroy_inode
2024/06/19 04:47 upstream 2ccbdf43d5e7 639d6cdf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root KASAN: user-memory-access Write in __destroy_inode
2024/06/05 12:04 upstream 32f88d65f01b e1e2c66e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root KASAN: user-memory-access Write in __destroy_inode
2024/05/04 19:23 upstream 7367539ad4b0 610f2a54 .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/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
2025/09/06 05:14 upstream c8ed9b5c02a5 d291dd2d .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root KASAN: user-memory-access Write in __destroy_inode
2025/08/24 21:48 upstream 69fd6b99b8f8 bf27483f .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root KASAN: user-memory-access Write in __destroy_inode
2025/08/12 11:46 upstream 53e760d89498 c06e8995 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root KASAN: user-memory-access Write in __destroy_inode
2025/07/26 10:38 upstream 5f33ebd2018c fb8f743d .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root KASAN: user-memory-access Write in __destroy_inode
2024/10/07 08:47 upstream 2a130b7e1fcd d7906eff .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root KASAN: user-memory-access Write in __destroy_inode
2024/06/26 10:21 upstream 55027e689933 dec8bc94 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream KASAN: user-memory-access Write in __destroy_inode
2024/06/25 13:04 upstream 55027e689933 c2e07261 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-qemu-upstream 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
2025/10/26 12:49 linux-next 72fb0170ef1f c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2024/07/14 22:48 linux-next 3fe121b62282 eaeb5c15 .config strace log report syz / log 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/07/14 20:54 linux-next 3fe121b62282 eaeb5c15 .config strace log report syz / log 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/07/14 18:59 linux-next 3fe121b62282 eaeb5c15 .config strace log report syz / log 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/07/14 16:57 linux-next 3fe121b62282 eaeb5c15 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root KASAN: user-memory-access Write in __destroy_inode
2025/12/07 21:31 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 05c93f3395ed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 KASAN: user-memory-access Write in __destroy_inode
2025/12/06 08:02 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 05c93f3395ed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 KASAN: user-memory-access Write in __destroy_inode
2025/12/03 15:43 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 05c93f3395ed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 KASAN: user-memory-access Write in __destroy_inode
2025/11/29 11:10 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 05c93f3395ed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 KASAN: user-memory-access Write in __destroy_inode
2025/11/25 14:25 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 3812f8fa7c83 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 KASAN: user-memory-access Write in __destroy_inode
2025/11/12 01:08 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 74c964729281 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 KASAN: user-memory-access Write in __destroy_inode
2025/10/25 13:39 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci b98c94eed4a9 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 KASAN: user-memory-access Write in __destroy_inode
2025/08/26 15:28 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8f5ae30d69d7 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 KASAN: user-memory-access Write in __destroy_inode
2025/08/20 20:59 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8f5ae30d69d7 bd178e57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 KASAN: user-memory-access Write in __destroy_inode
2025/08/14 05:56 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8f5ae30d69d7 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 KASAN: user-memory-access Write in __destroy_inode
2025/08/13 09:58 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8f5ae30d69d7 22ec1469 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-gce-arm64 KASAN: user-memory-access Write in __destroy_inode
2024/09/19 04:13 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 5f5673607153 c673ca06 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 KASAN: user-memory-access Write in __destroy_inode
2024/06/23 01:02 upstream 563a50672d8a c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 KASAN: wild-memory-access Write in __destroy_inode
2024/06/22 12:45 upstream 35bb670d65fc c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 KASAN: wild-memory-access Write in __destroy_inode
* Struck through repros no longer work on HEAD.