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: 743d, last: 149d
Cause bisection: failed (error log, bisect log)
▶ ▼ ✨ AI Jobs (10)
ID Workflow Result Correct Bug Created Started Finished Revision
dc0c2b1a assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/11/05 08:05 2026/11/05 08:05 2026/11/05 08:06 2ee8459f
69ed59dd assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/10/05 08:12 2026/10/05 08:12 2026/10/05 08:13 57bbd979
6f627988 assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/09/04 06:21 2026/09/04 06:21 2026/09/04 06:23 801f0966
bdd7b2fa assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/08/05 00:04 2026/08/05 00:04 2026/08/05 00:04 d4abbeac
31d96e6e assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/07/05 06:22 2026/07/05 06:22 2026/07/05 06:25 93f57954
0ed786b0 assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/06/18 05:55 2026/06/18 05:55 2026/06/18 05:58 b62b3ded
7eae8cbb assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/06/10 01:54 2026/06/10 01:54 2026/06/10 01:57 c36c07f6
0365682a assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/06/04 04:21 2026/06/04 04:21 2026/06/04 04:23 62fe1528
9a42e6db assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/06/01 21:43 2026/06/01 21:43 2026/06/01 21:46 386cc6da
d86530dc assessment-security 💥 WARNING in fanotify_handle_event (2) 2026/05/18 10:44 2026/05/18 10:44 2026/05/18 10:45 55156e84
▶ ▼ Discussions (10)
Title Replies (including bot) Last reply
[syzbot] Monthly exfat report (Jun 2026) 0 (1) 2026/06/21 20:32
[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 missing-backport -1 syz, C error 3 2d20h 445d 0/2 upstream: reported C repro on 2025/09/02 05:01
linux-5.15 WARNING in fanotify_handle_event origin:upstream -1 syz, C error 4 7d05h 501d 0/3 upstream: reported C repro on 2025/07/08 09:14
linux-6.1 WARNING in fanotify_handle_event origin:upstream missing-backport -1 syz, C error 5 75d 500d 0/3 upstream: reported C repro on 2025/07/08 10:20
upstream WARNING in fanotify_handle_event fs -1 syz, C done 5 2713d 2712d 12/29 fixed on 2019/07/10 21:40
▶ ▼ Last patch testing requests (10)
Created Duration User Patch Repo Result
2026/11/14 10:50 29m retest repro linux-next error job log
2026/11/11 21:27 24m retest repro upstream no crash job log log
2026/11/11 21:27 21m retest repro upstream report job log log
2026/10/10 04:52 15m retest repro upstream error job log
2026/10/10 01:57 16m retest repro upstream error job log
2026/10/10 01:57 24m retest repro upstream no crash job log log
2026/10/10 01:57 14m retest repro upstream error job log
2026/09/27 09:38 28m retest repro linux-next no crash job log log
2026/09/27 09:38 27m retest repro linux-next no crash job log log
2026/09/03 13:49 30m retest repro linux-next report job log log

Sample crash report:
loop0: detected capacity change from 0 to 128
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5308 at fs/notify/fanotify/fanotify.h:216 fanotify_info_copy_name fs/notify/fanotify/fanotify.h:216 [inline]
WARNING: CPU: 0 PID: 5308 at fs/notify/fanotify/fanotify.h:216 fanotify_alloc_name_event fs/notify/fanotify/fanotify.c:646 [inline]
WARNING: CPU: 0 PID: 5308 at fs/notify/fanotify/fanotify.h:216 fanotify_alloc_event fs/notify/fanotify/fanotify.c:810 [inline]
WARNING: CPU: 0 PID: 5308 at fs/notify/fanotify/fanotify.h:216 fanotify_handle_event+0x2eba/0x3c50 fs/notify/fanotify/fanotify.c:936
Modules linked in:
CPU: 0 UID: 0 PID: 5308 Comm: syz-executor207 Not tainted 6.12.0-rc6-syzkaller-00169-g906bd684e4b1 #0
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:646 [inline]
RIP: 0010:fanotify_alloc_event fs/notify/fanotify/fanotify.c:810 [inline]
RIP: 0010:fanotify_handle_event+0x2eba/0x3c50 fs/notify/fanotify/fanotify.c:936
Code: f6 ff ff e8 58 a4 6e ff 90 0f 0b 90 e9 c0 f7 ff ff e8 4a a4 6e ff 90 0f 0b 90 4c 8b 6c 24 10 e9 e7 f8 ff ff e8 37 a4 6e ff 90 <0f> 0b 90 4c 8b 6c 24 10 e9 04 fb ff ff e8 24 a4 6e ff 90 0f 0b 90
RSP: 0018:ffffc9000d0473e0 EFLAGS: 00010293
RAX: ffffffff82263629 RBX: ffffc9000d047844 RCX: ffff888000848000
RDX: 0000000000000000 RSI: 0000000000000ffd RDI: 00000000000000ff
RBP: ffffc9000d0475e0 R08: ffffffff82262f60 R09: 0000000000000000
R10: ffff888043bd8038 R11: ffffffff821d7890 R12: ffff888043bd8000
R13: 0000000000000ffd R14: ffff888043bd8000 R15: dffffc0000000000
FS:  0000555581eb6380(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020004000 CR3: 000000003600e000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 send_to_group fs/notify/fsnotify.c:394 [inline]
 fsnotify+0x1657/0x1f60 fs/notify/fsnotify.c:607
 __fsnotify_parent+0x4f5/0x5e0 fs/notify/fsnotify.c:264
 fsnotify_parent include/linux/fsnotify.h:96 [inline]
 fsnotify_file include/linux/fsnotify.h:131 [inline]
 fsnotify_open include/linux/fsnotify.h:401 [inline]
 vfs_open+0x28d/0x330 fs/open.c:1095
 do_open fs/namei.c:3774 [inline]
 path_openat+0x2c84/0x3590 fs/namei.c:3933
 do_filp_open+0x235/0x490 fs/namei.c:3960
 do_sys_openat2+0x13e/0x1d0 fs/open.c:1415
 do_sys_open fs/open.c:1430 [inline]
 __do_sys_creat fs/open.c:1508 [inline]
 __se_sys_creat fs/open.c:1502 [inline]
 __x64_sys_creat+0x123/0x170 fs/open.c:1502
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fde2034f6b9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff3d0c3658 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007fff3d0c3828 RCX: 00007fde2034f6b9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020003500
RBP: 00007fde203c3610 R08: 00007fff3d0c3828 R09: 00007fff3d0c3828
R10: 00007fff3d0c3828 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fff3d0c3818 R14: 0000000000000001 R15: 0000000000000001
 </TASK>

Crashes (31):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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/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/06/10 19:27 upstream acb7500801e9 f79bac11 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-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 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/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/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
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
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
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.