syzbot

 sign-in | mailing list | source | docs
🐞 Open [677]
🐞 Fixed [67]
🐞 Invalid [821]
⬇ Missing Backports [96]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

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: 374d, last: 19h30m
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 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! (3) net 2 1437d 1438d 20/28 fixed on 2021/11/10 00:50
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! (2) C done 5045 2022d 2191d 13/28 fixed on 2019/10/15 23:40
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! (4) bpf C done 31 6d17h 182d 0/28 upstream: reported C repro on 2024/09/27 03:52
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! C done 1725 2192d 2218d 11/28 fixed on 2019/03/28 12:00
linux-6.1 BUG: MAX_STACK_TRACE_ENTRIES too low! origin:upstream syz 1 6d13h 6d13h 0/3 upstream: reported syz repro on 2025/03/22 10:39
▶ ▼ Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/03/28 03:10 17m retest repro linux-5.15.y report log
2025/03/28 03:10 13m retest repro linux-5.15.y report log
2025/03/28 03:10 36m retest repro linux-5.15.y report log
2025/03/28 03:10 14m retest repro linux-5.15.y report log
2025/03/05 20:51 14m retest repro linux-5.15.y report log
2025/03/05 20:51 16m retest repro linux-5.15.y report log
2025/03/05 20:50 1h11m retest repro linux-5.15.y report log
2025/03/05 20:50 1h06m retest repro linux-5.15.y report log
2025/03/05 20:51 16m retest repro linux-5.15.y report log
2025/01/14 02:16 16m 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: 0 PID: 13 Comm: kworker/0:1 Not tainted 5.15.178-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: rcu_gp srcu_invoke_callbacks
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
 save_trace+0x88a/0xab0 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+0x28fa/0x5930 kernel/locking/lockdep.c:3788
 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012
 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162
 htab_lock_bucket kernel/bpf/hashtab.c:183 [inline]
 htab_lru_map_delete_elem+0x1c2/0x650 kernel/bpf/hashtab.c:1397
 bpf_prog_9dc0996bccb7470f+0x60/0xee0
 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+0x19e/0x340 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+0x22f/0x270 mm/slub.c:4549
 srcu_invoke_callbacks+0x1b9/0x400 kernel/rcu/srcutree.c:1272
 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
 kthread+0x3f6/0x4f0 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>

Crashes (30):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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!
* Struck through repros no longer work on HEAD.