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: 664d, last: 10d
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 (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 BUG: MAX_STACK_TRACE_ENTRIES too low! origin:lts-only -1 C inconclusive 2 18d 111d 0/2 upstream: reported C repro on 2025/09/23 14:36
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! (3) net -1 2 1727d 1728d 20/29 fixed on 2021/11/10 00:50
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! (2) -1 C done 5045 2312d 2481d 13/29 fixed on 2019/10/15 23:40
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! (4) bpf -1 C done unreliable 31 296d 472d 0/29 auto-obsoleted due to no activity on 2025/08/31 03:03
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! -1 C done 1725 2482d 2508d 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 4 37d 296d 0/3 upstream: reported C repro on 2025/03/22 10:39
Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/12/20 16:54 17m retest repro linux-5.15.y report log
2025/12/20 16:54 14m retest repro linux-5.15.y report log
2025/12/20 16:54 14m retest repro linux-5.15.y report log
2025/12/20 16:54 11m retest repro linux-5.15.y report log
2025/12/20 16:54 20m retest repro linux-5.15.y report log
2025/11/22 11:18 18m retest repro linux-5.15.y report log
2025/11/22 11:18 13m retest repro linux-5.15.y report log
2025/11/22 11:18 18m retest repro linux-5.15.y report log
2025/11/22 11:18 16m retest repro linux-5.15.y report log
2025/11/22 11:18 43m retest repro linux-5.15.y OK 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: 24742 Comm: syz-executor Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/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_lru_map_delete_elem+0x1b1/0x640 kernel/bpf/hashtab.c:1397
 bpf_prog_174bfe9d52de9121+0x47/0x320
 bpf_dispatcher_nop_func include/linux/bpf.h:888 [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
 trace_kfree include/trace/events/kmem.h:118 [inline]
 kfree+0x25f/0x2a0 mm/slub.c:4554
 tcp_saved_syn_free include/linux/tcp.h:488 [inline]
 tcp_v4_destroy_sock+0x4da/0x6e0 net/ipv4/tcp_ipv4.c:2329
 inet_csk_destroy_sock+0x15c/0x390 net/ipv4/inet_connection_sock.c:1051
 __tcp_close+0xbfb/0xfa0 net/ipv4/tcp.c:2911
 tcp_close+0x24/0x110 net/ipv4/tcp.c:2923
 inet_release+0x139/0x180 net/ipv4/af_inet.c:432
 __sock_release net/socket.c:651 [inline]
 sock_close+0xd5/0x240 net/socket.c:1346
 __fput+0x234/0x930 fs/file_table.c:311
 task_work_run+0x125/0x1a0 kernel/task_work.c:188
 tracehook_notify_resume include/linux/tracehook.h:189 [inline]
 exit_to_user_mode_loop+0x10f/0x130 kernel/entry/common.c:181
 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
 __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
 syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fecf7b303aa
Code: 48 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c 24 0c e8 43 91 02 00 8b 7c 24 0c 89 c2 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 d7 89 44 24 0c e8 a3 91 02 00 8b 44 24
RSP: 002b:00007ffd6a8647f0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000003 RCX: 00007fecf7b303aa
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00007ffd6a86484c R08: 00007ffd6a86414c R09: 00007ffd6a864557
R10: 00007ffd6a8641d0 R11: 0000000000000293 R12: 0000000000000108
R13: 00000000000927c0 R14: 00000000000a4676 R15: 00007ffd6a8648a0
 </TASK>

Crashes (43):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/01/02 13:19 linux-5.15.y 68efe5a6c16a d6526ea3 .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/12/06 14:19 linux-5.15.y cc5ec8769306 d6526ea3 .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/11/23 13:21 linux-5.15.y cc5ec8769306 4fb8ef37 .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/11/08 09:47 linux-5.15.y cc5ec8769306 4e1406b4 .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/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/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!
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!
* Struck through repros no longer work on HEAD.