From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-il1-f207.google.com (mail-il1-f207.google.com [209.85.166.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EFF0328B3E2 for ; Wed, 19 Nov 2025 20:44:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.166.207 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763585078; cv=none; b=X8R0cdW1uFUcnJDLIhQlKDtFYOL/EEm1gqnKvpfqbKVCIdqDoqoa6VqmZFfmRO3OcpstM/pTV2am0/3lBdok8A2VLLDzUDs9fv3u7DgDU7KkXIdAnLZHXXCl7GPmr4YZciGFmrNVu904silV8qTvbMUSar0X8pStuKXMkqknqJE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763585078; c=relaxed/simple; bh=+Z3+bLESk/0SzMVGNvnp7w2sq7gFUw5i0Gc58/GPqxM=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=leUluWiSVCNaNsZ0/wVwzbCwy6pIPsC3eZXrE8Bd2Xx4c7P0zxmaMevcApx+qOIcn0HiZc8/YAcOpHcJjPG6j8RKW/EGZCywJOBIF40+E1fAssJHn3WD/ZL0YHpMDIZivGZla0dS8cypoQapaVGEikNH98n0CJLhnwjpN34h/Fg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.166.207 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-il1-f207.google.com with SMTP id e9e14a558f8ab-433154d39abso3231165ab.0 for ; Wed, 19 Nov 2025 12:44:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763585075; x=1764189875; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=fVDtu/Rp+lPQNYcCVr4DUn+/8TyqiaxBRWusv82tbVI=; b=En52tiHVbP2FR9xXvinezPI5TD2YcIefdN8j744GGaHj/IBEFkDLDyaAD0O0XXE02w v3YmcOM7c+BFB2YQAyJZdlNNepSrPUVOogiW5Ep2Bpa4SXNCsj3eCQvy9dv9xyZ4MVPZ rMtCWy8j0Ql21IjImzBZ7dTEZQoRK6LDSwgdyo2pgmjS7vvF8nbwXTnncU4Utt5sz4kt /M0SV+tjESIXqfFQdh+iAePLJlTBiTip6VHFWNmt8iAfeGdg6eNc2Lqbk1rQ94y0NUp5 Z5LiFgmjW9LrS+a75t6MnURj3MnkRf3qZK5l2C8zCbseskSXdhFWBRefe82R3BbIrAxJ lJuA== X-Forwarded-Encrypted: i=1; AJvYcCUp2TT0hAr21foVFAAEkn0xL+R1bHVTEdIO1tsm8HCTIXFKOE9BCCz8dcpic8re+A51u2eMBrBcCz+IrmE=@vger.kernel.org X-Gm-Message-State: AOJu0YzIA1GZttbxPJBuk7nvVL2jB8anzsZ2RinD0qfVCD6dJU204OYH /7eH6i3zbXkICCx0ASUlCGX7c6pbfzV4xbegfD+6kp3iV2iabVBCMzKaBUeOuqbLQrg8Z31XOXE m4IxlNX1lp8eBrZYP9w2Cdw97SG6WXdiK3Bkbc4k8EMC7bUta7iy4GkRh8Jo= X-Google-Smtp-Source: AGHT+IGVn8GrEjKOPtV7FodlXsB1sfK4h090hAQK7DfVmBw3TNv7l6Tq/saj5WGXrhy3MxwrfIft9sd32Xh0dIijXWi6yrZ0cXHV Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6e02:218c:b0:433:7f29:929e with SMTP id e9e14a558f8ab-435a9e19c61mr3797525ab.31.1763585074928; Wed, 19 Nov 2025 12:44:34 -0800 (PST) Date: Wed, 19 Nov 2025 12:44:34 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <691e2c32.a70a0220.2ea503.0020.GAE@google.com> Subject: [syzbot] [bpf?] WARNING: kmalloc bug in bpf_prog_alloc_no_stats From: syzbot To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net, eddyz87@gmail.com, haoluo@google.com, john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org, linux-kernel@vger.kernel.org, martin.lau@linux.dev, sdf@fomichev.me, song@kernel.org, syzkaller-bugs@googlegroups.com, yonghong.song@linux.dev Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 0c1c7a6a83fe Add linux-next specific files for 20251117 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=12c86692580000 kernel config: https://syzkaller.appspot.com/x/.config?x=78555cc0f7025c00 dashboard link: https://syzkaller.appspot.com/bug?extid=d4264133b3e51212ea30 compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/30639e6c3546/disk-0c1c7a6a.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/88fdcd914c22/vmlinux-0c1c7a6a.xz kernel image: https://storage.googleapis.com/syzbot-assets/087028e72d0f/bzImage-0c1c7a6a.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+d4264133b3e51212ea30@syzkaller.appspotmail.com ------------[ cut here ]------------ Unexpected gfp: 0x400000 (__GFP_ACCOUNT). Fixing up to gfp: 0xdc0 (GFP_KERNEL|__GFP_ZERO). Fix your code! WARNING: mm/vmalloc.c:3938 at vmalloc_fix_flags+0x9c/0xe0 mm/vmalloc.c:3937, CPU#1: syz-executor/6076 Modules linked in: CPU: 1 UID: 0 PID: 6076 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 RIP: 0010:vmalloc_fix_flags+0x9c/0xe0 mm/vmalloc.c:3937 Code: 81 e6 1f 52 ee ff 89 74 24 30 81 e3 e0 ad 11 00 89 5c 24 20 90 48 c7 c7 a0 db 96 8b 4c 89 fa 89 d9 4d 89 f0 e8 85 8d 6c ff 90 <0f> 0b 90 90 8b 44 24 20 48 c7 04 24 0e 36 e0 45 4b c7 04 2c 00 00 RSP: 0018:ffffc900043cfb00 EFLAGS: 00010246 RAX: a51e1d8e991b0100 RBX: 0000000000000dc0 RCX: ffff888031d2bd00 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002 RBP: ffffc900043cfb98 R08: ffffc900043cf827 R09: 1ffff92000879f04 R10: dffffc0000000000 R11: fffff52000879f05 R12: 1ffff92000879f60 R13: dffffc0000000000 R14: ffffc900043cfb20 R15: ffffc900043cfb30 FS: 0000555589c86500(0000) GS:ffff888125b74000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fa89645c470 CR3: 0000000079642000 CR4: 00000000003526f0 Call Trace: __vmalloc_noprof+0xf2/0x120 mm/vmalloc.c:4124 bpf_prog_alloc_no_stats+0x4a/0x4d0 kernel/bpf/core.c:106 bpf_prog_alloc+0x3c/0x1a0 kernel/bpf/core.c:153 bpf_prog_create_from_user+0xa7/0x440 net/core/filter.c:1443 seccomp_prepare_filter kernel/seccomp.c:701 [inline] seccomp_prepare_user_filter kernel/seccomp.c:738 [inline] seccomp_set_mode_filter kernel/seccomp.c:1990 [inline] do_seccomp+0x7b1/0xd90 kernel/seccomp.c:2110 __do_sys_prctl kernel/sys.c:2610 [inline] __se_sys_prctl+0xc3c/0x1830 kernel/sys.c:2518 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fa896590b0d Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 18 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 9d 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 1b 48 8b 54 24 18 64 48 2b 14 25 28 00 00 00 RSP: 002b:00007ffe0659e8d0 EFLAGS: 00000246 ORIG_RAX: 000000000000009d RAX: ffffffffffffffda RBX: 00007fa89662cf80 RCX: 00007fa896590b0d RDX: 00007ffe0659e930 RSI: 0000000000000002 RDI: 0000000000000016 RBP: 00007ffe0659e940 R08: 0000000000000006 R09: 0000000000000071 R10: 0000000000000071 R11: 0000000000000246 R12: 000000000000006d R13: 00007ffe0659ed68 R14: 00007ffe0659efe8 R15: 0000000000000000 --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup