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: 268d, last: 12d
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 (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! (3) net 2 1331d 1332d 20/28 fixed on 2021/11/10 00:50
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! (2) C done 5045 1916d 2085d 13/28 fixed on 2019/10/15 23:40
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! (4) bpf C done 11 3d08h 76d 0/28 upstream: reported C repro on 2024/09/27 03:52
upstream BUG: MAX_STACK_TRACE_ENTRIES too low! C done 1725 2086d 2112d 11/28 fixed on 2019/03/28 12:00
Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/11/30 15:49 15m retest repro linux-5.15.y report log
2024/11/30 15:49 12m retest repro linux-5.15.y report log
2024/11/16 12:01 20m retest repro linux-5.15.y report log
2024/11/16 12:01 20m retest repro linux-5.15.y report log
2024/11/16 12:01 15m retest repro linux-5.15.y report log
2024/11/16 12:01 58m retest repro linux-5.15.y report log
2024/11/16 12:02 15m retest repro linux-5.15.y report log
2024/10/27 10:29 15m retest repro linux-5.15.y report log
2024/10/27 10:29 18m retest repro linux-5.15.y report log
2024/10/27 10:29 20m 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: 4165 Comm: syz-executor126 Not tainted 5.15.170-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
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_2c29ac5cdc6b1842+0x3a/0xbc
 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
 __traceiter_kfree+0x26/0x40 include/trace/events/kmem.h:118
 trace_kfree include/trace/events/kmem.h:118 [inline]
 kfree+0x22f/0x270 mm/slub.c:4549
 fscrypt_free_filename include/linux/fscrypt.h:316 [inline]
 ext4_fname_free_filename fs/ext4/ext4.h:2784 [inline]
 ext4_add_entry+0xe1a/0x12b0 fs/ext4/namei.c:2527
 ext4_mkdir+0x54f/0xce0 fs/ext4/namei.c:3081
 vfs_mkdir+0x3b6/0x590 fs/namei.c:4065
 do_mkdirat+0x260/0x520 fs/namei.c:4090
 __do_sys_mkdir fs/namei.c:4110 [inline]
 __se_sys_mkdir fs/namei.c:4108 [inline]
 __x64_sys_mkdir+0x6a/0x80 fs/namei.c:4108
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fe736f7ee87
Code: 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 53 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcb9dbf3b8 EFLAGS: 00000206 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00000000000057b6 RCX: 00007fe736f7ee87
RDX: 0000000000000000 RSI: 00000000000001ff RDI: 00007ffcb9dbf430
RBP: 00007ffcb9dbf3d4 R08: 0000000000000006 R09: 00007ffcb9dbf154
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000737
R13: 431bde82d7b634db R14: 000000000002bbe0 R15: 00007ffcb9dbf430
 </TASK>

Crashes (20):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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!
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.