syzbot


BUG: MAX_STACK_TRACE_ENTRIES too low!

Status: upstream: reported C repro on 2024/03/19 07:46
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+d83eeff73983945eae3d@syzkaller.appspotmail.com
First crash: 517d, last: 6d09h
Fix commit to backport (bisect log) :
tree: upstream
commit 1022a5498f6f745c3b5fd3f050a5e11e7ca354f0
Author: Song Liu <songliubraving@fb.com>
Date: Fri Feb 4 18:57:42 2022 +0000

  bpf, x86_64: Use bpf_jit_binary_pack_alloc

  
Bug presence (2)
Date Name Commit Repro Result
2024/05/02 linux-5.15.y (ToT) b925f60c6ee7 C [report] BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/05/02 upstream (ToT) 0106679839f7 C Didn't crash
Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! (3) net -1 2 1580d 1581d 20/29 fixed on 2021/11/10 00:50
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! (2) -1 C done 5045 2165d 2334d 13/29 fixed on 2019/10/15 23:40
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! (4) bpf -1 C done unreliable 31 149d 325d 0/29 upstream: reported C repro on 2024/09/27 03:52
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! -1 C done 1725 2335d 2361d 11/29 fixed on 2019/03/28 12:00
linux-6.1 BUG: MAX_STACK_TRACE_ENTRIES too low! origin:lts-only -1 C inconclusive 2 43d 149d 0/3 upstream: reported C repro on 2025/03/22 10:39
Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/08/02 16:01 15m retest repro linux-5.15.y report log
2025/08/02 16:01 16m retest repro linux-5.15.y report log
2025/08/02 16:01 12m retest repro linux-5.15.y report log
2025/08/02 16:01 16m retest repro linux-5.15.y report log
2025/08/02 16:01 15m retest repro linux-5.15.y report log
2025/07/19 06:33 14m retest repro linux-5.15.y report log
2025/07/19 06:33 14m retest repro linux-5.15.y report log
2025/07/19 06:33 15m retest repro linux-5.15.y report log
2025/07/19 06:33 18m retest repro linux-5.15.y report log
2025/07/19 06:33 12m retest repro linux-5.15.y report log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2024/05/14 09:46 7h38m fix candidate upstream OK (1) job log

Sample crash report:
BUG: MAX_STACK_TRACE_ENTRIES too low!
turning off the locking correctness validator.
CPU: 1 PID: 18732 Comm: udevd Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 save_trace+0x85f/0xa80 kernel/locking/lockdep.c:547
 check_prev_add kernel/locking/lockdep.c:3114 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x3b0b/0x7c60 kernel/locking/lockdep.c:5012
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0xa4/0xf0 kernel/locking/spinlock.c:162
 htab_lock_bucket kernel/bpf/hashtab.c:183 [inline]
 htab_map_delete_elem+0x1b2/0x520 kernel/bpf/hashtab.c:1361
 bpf_prog_18062990963791d1+0x5d/0x79c
 bpf_dispatcher_nop_func include/linux/bpf.h:790 [inline]
 __bpf_prog_run include/linux/filter.h:628 [inline]
 bpf_prog_run include/linux/filter.h:635 [inline]
 __bpf_trace_run kernel/trace/bpf_trace.c:1878 [inline]
 bpf_trace_run2+0x15b/0x2d0 kernel/trace/bpf_trace.c:1915
 __bpf_trace_kfree+0x6e/0x90 include/trace/events/kmem.h:118
 __traceiter_kfree+0x26/0x40 include/trace/events/kmem.h:118
 trace_kfree include/trace/events/kmem.h:118 [inline]
 kfree+0x25f/0x2a0 mm/slub.c:4549
 tomoyo_realpath_from_path+0x10b/0x610 security/tomoyo/realpath.c:253
 tomoyo_get_realpath security/tomoyo/file.c:151 [inline]
 tomoyo_path_perm+0x1cd/0x510 security/tomoyo/file.c:822
 tomoyo_path_unlink+0x9f/0xe0 security/tomoyo/tomoyo.c:149
 security_path_unlink+0xd8/0x130 security/security.c:1170
 do_unlinkat+0x2ed/0x6f0 fs/namei.c:4344
 __do_sys_unlink fs/namei.c:4396 [inline]
 __se_sys_unlink fs/namei.c:4394 [inline]
 __x64_sys_unlink+0x45/0x50 fs/namei.c:4394
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f63dfcf2937
Code: 00 00 e9 a9 fd ff ff 66 2e 0f 1f 84 00 00 00 00 00 66 90 b8 5f 00 00 00 0f 05 c3 0f 1f 84 00 00 00 00 00 b8 57 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 91 b4 0d 00 f7 d8 64 89 02 b8
RSP: 002b:00007ffd24d21688 EFLAGS: 00000206 ORIG_RAX: 0000000000000057
RAX: ffffffffffffffda RBX: 000056469ae7b500 RCX: 00007f63dfcf2937
RDX: 0000000000000001 RSI: 000056466cd2767f RDI: 00007ffd24d21690
RBP: 0000000000001613 R08: 0000000000000064 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 00007ffd24d21690
R13: 0000000003938700 R14: 000056466cd42100 R15: 000056466cd42140
 </TASK>

Crashes (39):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/12 02:54 linux-5.15.y c79648372d02 c06e8995 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/06/05 17:11 linux-5.15.y 1c700860e8bc 6b6b5f21 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/06/05 11:12 linux-5.15.y 1c700860e8bc 6b6b5f21 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/05/22 20:22 linux-5.15.y 98f47d0e9b8c 0919b50b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/05/03 08:58 linux-5.15.y 16fdf2c7111b b0714e37 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/04/14 08:35 linux-5.15.y f7347f400572 0bd6db41 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/04/06 23:38 linux-5.15.y 0c935c049b5c 1c65791e .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/04/05 11:19 linux-5.15.y 0c935c049b5c c53ea9c9 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/03/13 04:32 linux-5.15.y c16c81c81336 1a5d9317 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/02/19 14:02 linux-5.15.y c16c81c81336 9a14138f .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/02/14 18:47 linux-5.15.y c16c81c81336 1022af74 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/02/10 21:17 linux-5.15.y c16c81c81336 43f51a00 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/02/08 12:20 linux-5.15.y c16c81c81336 ef44b750 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/02/07 18:22 linux-5.15.y c16c81c81336 53657d1b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/01/31 14:11 linux-5.15.y 003148680b79 4c6ac32f .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/01/23 02:18 linux-5.15.y 4735586da88e a44b0418 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/01/18 17:32 linux-5.15.y 4735586da88e f2cb035c .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/11/02 05:50 linux-5.15.y 72244eab0dad f00eed24 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/09/29 02:16 linux-5.15.y 3a5928702e71 ba29ff75 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/09/28 06:36 linux-5.15.y 3a5928702e71 440b26ec .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/09/24 04:06 linux-5.15.y 3a5928702e71 89298aad .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/09/20 23:01 linux-5.15.y 3a5928702e71 6f888b75 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/09/18 17:18 linux-5.15.y 3a5928702e71 c673ca06 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/09/17 03:07 linux-5.15.y 3a5928702e71 c673ca06 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/09/08 03:01 linux-5.15.y 14e468424d3e 9750182a .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/09/07 09:15 linux-5.15.y 14e468424d3e 9750182a .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/09/06 07:44 linux-5.15.y 14e468424d3e 464ac2ed .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/08/31 19:39 linux-5.15.y fa93fa65db6e 1eda0d14 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/07/03 03:54 linux-5.15.y 4878aadf2d15 07f0a0a0 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/06/23 22:10 linux-5.15.y 4878aadf2d15 edc5149a .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/04/02 20:39 linux-5.15.y 9465fef4ae35 eb2966c4 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/03/29 20:37 linux-5.15.y 9465fef4ae35 c52bcb23 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/03/21 04:36 linux-5.15.y b95c01af2113 5b7d42ae .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/03/21 00:42 linux-5.15.y b95c01af2113 5b7d42ae .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/03/19 07:45 linux-5.15.y b95c01af2113 baa80228 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/03/31 15:48 linux-5.15.y 0c935c049b5c d3999433 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: MAX_STACK_TRACE_ENTRIES too low!
2025/01/19 21:25 linux-5.15.y 4735586da88e f2cb035c .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/07/18 04:06 linux-5.15.y f45bea23c39c 0f902625 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: MAX_STACK_TRACE_ENTRIES too low!
2024/07/03 01:10 linux-5.15.y 4878aadf2d15 07f0a0a0 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: MAX_STACK_TRACE_ENTRIES too low!
* Struck through repros no longer work on HEAD.