syzbot

 sign-in | mailing list | source | docs | 🏰
🐞 Open [1333]
≡ Subsystems
🐞 Fixed [7143]
🐞 Invalid [18890]
⬇ Missing Backports [220]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
Total Repo Heatmap Subsystems Heatmap
✨ AI
💬 Send us feedback

WARNING in fanotify_handle_event (2)

Status: upstream: reported C repro on 2024/11/12 04:21
Subsystems: exfat
[Documentation on labels]
Reported-by: syzbot+318aab2cf26bb7d40228@syzkaller.appspotmail.com
First crash: 577d, last: 1d03h
Cause bisection: failed (error log, bisect log)
  
▶ ▼ ✨ AI Jobs (3)
ID Workflow Result Correct Bug Created Started Finished Revision Error
0365682a-7487-48b5-99e7-4a6f873be70a assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/06/04 04:21 2026/06/04 04:21 2026/06/04 04:23 62fe15281f5011cd203d8845b8767b10e7443aa5 failed to run ["make" "KERNELVERSION=syzkaller" "KERNELRELEASE=syzkaller" "LOCALVERSION=-syzkaller" "-j" "32" "ARCH=x86_64" "CC=ccache clang" "LD=ld.lld" "O=/app/workdir/cache/build/345e698bff5cb9e4a24c19e736116d07cbc9f401" "-s" "bzImage" "compile_commands.json"]: exit status 2 Root cause: error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` error: aborting due to 2 previous errors * * Restart config... * * * Memory initialization * Initialize kernel stack variables at function entry 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE) 2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) > 3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) choice[1-3?]: 3 Poison kernel stack before returning from syscalls (KSTACK_ERASE) [N/y/?] (NEW) Error in reading or end of file. Enable heap memory zeroing on allocation by default (INIT_ON_ALLOC_DEFAULT_ON) [Y/n/?] y Enable heap memory zeroing on free by default (INIT_ON_FREE_DEFAULT_ON) [N/y/?] n Enable register zeroing on function exit (ZERO_CALL_USED_REGS) [N/y/?] n error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/ff7a0e8a0c15d81a30376c377a8d0060ee790e74/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `core` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `core` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/ff7a0e8a0c15d81a30376c377a8d0060ee790e74/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `compiler_builtins` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `compiler_builtins` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: aborting due to 2 previous errors make[3]: *** [/app/workdir/cache/src/ff7a0e8a0c15d81a30376c377a8d0060ee790e74/rust/Makefile:527: rust/build_error.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[2]: *** [/app/workdir/cache/src/ff7a0e8a0c15d81a30376c377a8d0060ee790e74/Makefile:1286: prepare] Error 2 make[1]: *** [/app/workdir/cache/src/ff7a0e8a0c15d81a30376c377a8d0060ee790e74/Makefile:248: __sub-make] Error 2 make: *** [Makefile:248: __sub-make] Error 2
9a42e6db-4ca4-4902-8b4f-59d0e8daf2ca assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/06/01 21:43 2026/06/01 21:43 2026/06/01 21:46 386cc6dacdf7e3ebce9507beed6755d7e999554d failed to run ["make" "KERNELVERSION=syzkaller" "KERNELRELEASE=syzkaller" "LOCALVERSION=-syzkaller" "-j" "32" "ARCH=x86_64" "CC=ccache clang" "LD=ld.lld" "O=/app/workdir/cache/build/345e698bff5cb9e4a24c19e736116d07cbc9f401" "-s" "bzImage" "compile_commands.json"]: exit status 2 Root cause: error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` error: aborting due to 2 previous errors * * Restart config... * * * Memory initialization * Initialize kernel stack variables at function entry 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE) 2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) > 3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) choice[1-3?]: 3 Poison kernel stack before returning from syscalls (KSTACK_ERASE) [N/y/?] (NEW) Error in reading or end of file. Enable heap memory zeroing on allocation by default (INIT_ON_ALLOC_DEFAULT_ON) [Y/n/?] y Enable heap memory zeroing on free by default (INIT_ON_FREE_DEFAULT_ON) [N/y/?] n Enable register zeroing on function exit (ZERO_CALL_USED_REGS) [N/y/?] n error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/ff7a0e8a0c15d81a30376c377a8d0060ee790e74/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `core` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `core` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/ff7a0e8a0c15d81a30376c377a8d0060ee790e74/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `compiler_builtins` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `compiler_builtins` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: aborting due to 2 previous errors make[3]: *** [/app/workdir/cache/src/ff7a0e8a0c15d81a30376c377a8d0060ee790e74/rust/Makefile:527: rust/build_error.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[2]: *** [/app/workdir/cache/src/ff7a0e8a0c15d81a30376c377a8d0060ee790e74/Makefile:1286: prepare] Error 2 make[1]: *** [/app/workdir/cache/src/ff7a0e8a0c15d81a30376c377a8d0060ee790e74/Makefile:248: __sub-make] Error 2 make: *** [Makefile:248: __sub-make] Error 2
d86530dc-c1c0-4679-8fc8-5212af34a8c4 assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/05/18 10:44 2026/05/18 10:44 2026/05/18 10:45 55156e845761fb36809c4b3701a920dddce23332 failed to run ["make" "KERNELVERSION=syzkaller" "KERNELRELEASE=syzkaller" "LOCALVERSION=-syzkaller" "-j" "32" "ARCH=x86_64" "CC=ccache clang" "LD=ld.lld" "O=/app/workdir/cache/build/345e698bff5cb9e4a24c19e736116d07cbc9f401" "-s" "bzImage" "compile_commands.json"]: exit status 2 Root cause: error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` error: aborting due to 2 previous errors * * Restart config... * * * Memory initialization * Initialize kernel stack variables at function entry 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE) 2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) > 3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) choice[1-3?]: 3 Poison kernel stack before returning from syscalls (KSTACK_ERASE) [N/y/?] (NEW) Error in reading or end of file. Enable heap memory zeroing on allocation by default (INIT_ON_ALLOC_DEFAULT_ON) [Y/n/?] y Enable heap memory zeroing on free by default (INIT_ON_FREE_DEFAULT_ON) [N/y/?] n Enable register zeroing on function exit (ZERO_CALL_USED_REGS) [N/y/?] n error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/00228d58104c15173068258912b236d547796ddb/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `core` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `core` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/00228d58104c15173068258912b236d547796ddb/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `compiler_builtins` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `compiler_builtins` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: aborting due to 2 previous errors make[3]: *** [/app/workdir/cache/src/00228d58104c15173068258912b236d547796ddb/rust/Makefile:527: rust/build_error.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[2]: *** [/app/workdir/cache/src/00228d58104c15173068258912b236d547796ddb/Makefile:1286: prepare] Error 2 make[1]: *** [/app/workdir/cache/src/00228d58104c15173068258912b236d547796ddb/Makefile:248: __sub-make] Error 2 make: *** [Makefile:248: __sub-make] Error 2
▶ ▼ Discussions (9)
Title Replies (including bot) Last reply
[syzbot] Monthly exfat report (May 2026) 0 (1) 2026/05/16 20:32
[syzbot] Monthly exfat report (Apr 2026) 0 (1) 2026/04/15 12:39
[syzbot] Monthly exfat report (Mar 2026) 0 (1) 2026/03/16 10:43
[syzbot] Monthly exfat report (Feb 2026) 0 (1) 2026/02/11 20:33
[syzbot] Monthly exfat report (Jan 2026) 0 (1) 2026/01/12 08:40
[syzbot] Monthly exfat report (Dec 2025) 0 (1) 2025/12/01 10:41
[syzbot] Monthly exfat report (Sep 2025) 0 (1) 2025/09/26 18:13
[syzbot] Monthly exfat report (Jul 2025) 0 (1) 2025/07/26 08:56
[syzbot] [fs?] WARNING in fanotify_handle_event (2) 1 (2) 2024/11/12 11:50
▶ ▼ Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 WARNING in fanotify_handle_event origin:upstream -1 C error 3 7d21h 279d 0/2 upstream: reported C repro on 2025/09/02 05:01
linux-5.15 WARNING in fanotify_handle_event origin:upstream -1 C error 4 17d 335d 0/3 upstream: reported C repro on 2025/07/08 09:14
linux-6.1 WARNING in fanotify_handle_event origin:upstream -1 C error 5 164d 335d 0/3 upstream: reported C repro on 2025/07/08 10:20
upstream WARNING in fanotify_handle_event fs -1 C done 5 2547d 2546d 12/29 fixed on 2019/07/10 21:40
▶ ▼ Last patch testing requests (10)
Created Duration User Patch Repo Result
2026/05/22 23:57 23m retest repro upstream log
2026/05/22 23:57 24m retest repro upstream error
2026/05/22 23:57 24m retest repro upstream log
2026/05/22 23:57 24m retest repro upstream error
2026/05/08 22:17 57m retest repro linux-next report log
2026/05/08 22:17 1h03m retest repro linux-next report log
2026/04/05 17:04 17m retest repro linux-next report log
2026/04/05 16:29 17m retest repro upstream log
2026/03/09 14:36 19m retest repro upstream report log
2026/03/09 14:36 17m retest repro upstream error

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5640 at fs/notify/fanotify/fanotify.h:216 fanotify_info_copy_name fs/notify/fanotify/fanotify.h:216 [inline]
WARNING: CPU: 0 PID: 5640 at fs/notify/fanotify/fanotify.h:216 fanotify_alloc_name_event fs/notify/fanotify/fanotify.c:686 [inline]
WARNING: CPU: 0 PID: 5640 at fs/notify/fanotify/fanotify.h:216 fanotify_alloc_event fs/notify/fanotify/fanotify.c:851 [inline]
WARNING: CPU: 0 PID: 5640 at fs/notify/fanotify/fanotify.h:216 fanotify_handle_event+0x30bf/0x3cc0 fs/notify/fanotify/fanotify.c:982
Modules linked in:
CPU: 0 UID: 0 PID: 5640 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:fanotify_info_copy_name fs/notify/fanotify/fanotify.h:216 [inline]
RIP: 0010:fanotify_alloc_name_event fs/notify/fanotify/fanotify.c:686 [inline]
RIP: 0010:fanotify_alloc_event fs/notify/fanotify/fanotify.c:851 [inline]
RIP: 0010:fanotify_handle_event+0x30bf/0x3cc0 fs/notify/fanotify/fanotify.c:982
Code: f8 ff ff e8 93 da 72 ff 90 0f 0b 90 e9 3e f9 ff ff e8 85 da 72 ff 90 0f 0b 90 4c 8b 64 24 08 e9 62 fa ff ff e8 72 da 72 ff 90 <0f> 0b 90 e9 f4 fb ff ff e8 64 da 72 ff 90 0f 0b 90 e9 9d fd ff ff
RSP: 0018:ffffc9000d2bf8a0 EFLAGS: 00010293
RAX: ffffffff824d791e RBX: 0000000000000ffd RCX: ffff888034962480
RDX: 0000000000000000 RSI: 0000000000000ffd RDI: 00000000000000ff
RBP: ffffc9000d2bfa80 R08: 0000000000000002 R09: 0000000000000000
R10: ffff888050d04038 R11: ffffffff8244c590 R12: 0000000000000ffd
R13: 1ffff92001a57f2c R14: ffffc9000d2bfca0 R15: ffff888050d04000
FS:  00007f93075f66c0(0000) GS:ffff88808d301000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9308179460 CR3: 0000000051767000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 send_to_group fs/notify/fsnotify.c:420 [inline]
 fsnotify+0x1412/0x1a80 fs/notify/fsnotify.c:641
 __fsnotify_parent+0x3fe/0x540 fs/notify/fsnotify.c:287
 fsnotify_parent include/linux/fsnotify.h:96 [inline]
 fsnotify_path include/linux/fsnotify.h:113 [inline]
 fsnotify_file include/linux/fsnotify.h:127 [inline]
 fsnotify_close include/linux/fsnotify.h:457 [inline]
 __fput+0x34e/0xa70 fs/file_table.c:454
 task_work_run+0x1d4/0x260 kernel/task_work.c:227
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 exit_to_user_mode_loop+0xe9/0x130 kernel/entry/common.c:43
 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline]
 syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline]
 do_syscall_64+0x2bd/0xfa0 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9307f8eec9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f93075f6038 EFLAGS: 00000246 ORIG_RAX: 000000000000003b
RAX: fffffffffffffff8 RBX: 00007f93081e5fa0 RCX: 00007f9307f8eec9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000440
RBP: 00007f9308011f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f93081e6038 R14: 00007f93081e5fa0 R15: 00007fff2305f618
 </TASK>

Crashes (30):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/10/14 10:30 upstream 3a8660878839 b6605ba8 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2025/06/19 00:51 upstream 52da431bf03b ed3e87f7 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2024/11/08 05:59 upstream 906bd684e4b1 179b040e .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2024/11/08 05:20 upstream 906bd684e4b1 179b040e .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2024/11/08 04:43 upstream 906bd684e4b1 179b040e .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2026/04/24 10:50 linux-next 4c406406070d 9cfb3ca7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-linux-next-kasan-gce-root WARNING in fanotify_handle_event
2026/04/24 05:46 linux-next 4c406406070d 9cfb3ca7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-linux-next-kasan-gce-root WARNING in fanotify_handle_event
2026/01/08 21:26 linux-next fc4e91c639c0 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-linux-next-kasan-gce-root WARNING in fanotify_handle_event
2026/03/22 16:14 upstream 113ae7b4decc 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING in fanotify_handle_event
2025/07/08 10:22 upstream d7b8f8e20813 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root WARNING in fanotify_handle_event
2025/07/08 10:21 upstream d7b8f8e20813 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root WARNING in fanotify_handle_event
2025/07/08 08:27 upstream d7b8f8e20813 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING in fanotify_handle_event
2025/07/08 08:27 upstream d7b8f8e20813 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING in fanotify_handle_event
2026/06/07 09:14 upstream 8e65320d91cd cc095639 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2026/04/23 22:28 upstream 2e6803928193 629ff21a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2026/02/23 13:56 upstream 6de23f81a5e0 7c9658af .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2026/02/14 11:01 upstream 770aaedb461a 1e62d198 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2026/02/01 04:32 upstream 162b42445b58 6b8752f2 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2026/02/01 02:12 upstream 162b42445b58 6b8752f2 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2025/11/22 08:17 upstream 2eba5e05d9bc 4fb8ef37 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2025/11/08 16:53 upstream e811c33b1f13 4e1406b4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2025/10/14 09:08 upstream 3a8660878839 b6605ba8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2025/09/22 18:15 upstream 07e27ad16399 770ff59f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2025/07/08 07:49 upstream d7b8f8e20813 4f67c4ae .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2025/06/18 23:46 upstream 52da431bf03b ed3e87f7 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2025/01/08 08:23 upstream 09a0fa92e5b4 f3558dbf .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2024/11/08 04:15 upstream 906bd684e4b1 179b040e .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in fanotify_handle_event
2025/07/08 08:40 linux-next 26ffb3d6f02c 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root WARNING in fanotify_handle_event
2025/09/01 20:14 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8f5ae30d69d7 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 WARNING in fanotify_handle_event
2025/02/14 11:40 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a64dcfb451e2 d9a046cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 WARNING in fanotify_handle_event
* Struck through repros no longer work on HEAD.