From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-io1-f69.google.com (mail-io1-f69.google.com [209.85.166.69]) (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 AB93D329E51 for ; Thu, 13 Nov 2025 07:41:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.166.69 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763019701; cv=none; b=YOcEjZmbgieiThGg0lmiotxxfz8iklaip/UKAUvQp7Hs3yg9qWqg2RIMjDlDSXqjyiMICY/1xkVw8K064ot2mOW5Ra/efm8uDwOu+V8YccmipnWwX1c8wcGK/uKQRV7Ga0/edWAmqEGIxzHlCJzGImsOKaUdpjTe9/7rQC1w3HU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763019701; c=relaxed/simple; bh=wL3ajtIbhIl7uczCpuXPKbOTU1CBaLDkdZK72JB/MnQ=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To:Cc: Content-Type; b=HBAkZIwJreoqwKey75RVoNXiD/cfIyjA9/uJSf2/RE4rEruYNUeFwZvFKL3pkuKDcNPdGNdvcuit/FejpemJ8CGqMzLIuYkNLHb3uwAOkDw0+hNDcIwdFpjRXHqJVFqu8t+ieIrQanTpFl6S28goAKibYEEvJ5wU2HC4PkiCDMw= 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.69 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-io1-f69.google.com with SMTP id ca18e2360f4ac-9489e3680bfso62748639f.2 for ; Wed, 12 Nov 2025 23:41:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763019697; x=1763624497; h=cc:to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=jWzdKl7vgdIGJfdYX6z8A/NZowwAqQ9vSHhm0lIHqaA=; b=nECnPlKfGD0kl12gI1OGl9buB/1NH4UTAAR6OcC/TSGe8Qpa8zetgmL+It8gNew2M0 akJNM7mSqfCtOOKBhUE/cYW4c9eUFaeJtnFOs9gIrDmjILwJ6slb1mAdib/DngMcRRFw fLF4zjl2qFsr+o3YA7+8inmPy7Fi+YfM6Vinc51Aq/6FJ1kHJf88e1CSkDzl1xolP1xu aemKBzflWPvkzS3akesT8ZxEx/APo0EhJRfIPRJ6MPHWiyKQ3RiIoW/rjGeq5E+w0g6F EnthNnvuC0mZCIo/Cw8gs3ETs/JTNaggz6krbu9GTpMDAvsEfE9hzKLMm9+jagxatLbN mGTw== X-Forwarded-Encrypted: i=1; AJvYcCWQSDhO1naWh1N9aufQSjdxu8oKeT9tRPVds01tM6w8yKgydFb23DR5iHkHo2WMXe7i5r2drSvCm9c0S3s=@vger.kernel.org X-Gm-Message-State: AOJu0YwMr6HeCUSyUgrRParhGbRbS6V37fFyRV+hx4dJ/fiySPWGZDLx /ixM2aqnwBkYW8hDivXvdD5l987HQUQxFjqF+dHqMlKsJ21XFkz6BsJeiiacAu93aNkyitB86PW FKl+RGik92nvW1LFDPTxu5vWjaN7UoAG/gajB2sMUqC2R6ooKc4usJCQWW3I= X-Google-Smtp-Source: AGHT+IG3FVRXoV3IJYse4nKZ7YA6tLNSXRmqIqWo6eFJ4/fcr5tzXzRXuvajfRcvKmFz7PDAabk2bViR8Eeqb1Oz5r5xzHzojmQl 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:2283:b0:433:2812:8066 with SMTP id e9e14a558f8ab-43473ddd4edmr74082945ab.23.1763019697635; Wed, 12 Nov 2025 23:41:37 -0800 (PST) Date: Wed, 12 Nov 2025 23:41:37 -0800 In-Reply-To: <20251112185834.32487-1-vishal.moola@gmail.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69158bb1.a70a0220.3124cb.001e.GAE@google.com> Subject: [syzbot ci] Re: make vmalloc gfp flags usage more apparent From: syzbot ci To: akpm@linux-foundation.org, bpf@vger.kernel.org, hch@infradead.org, hch@lst.de, linux-kernel@vger.kernel.org, linux-mm@kvack.org, urezki@gmail.com, vishal.moola@gmail.com Cc: syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" syzbot ci has tested the following series [v2] make vmalloc gfp flags usage more apparent https://lore.kernel.org/all/20251112185834.32487-1-vishal.moola@gmail.com * [PATCH v2 1/4] mm/vmalloc: warn on invalid vmalloc gfp flags * [PATCH v2 2/4] mm/vmalloc: Add a helper to optimize vmalloc allocation gfps * [PATCH v2 3/4] mm/vmalloc: cleanup large_gfp in vm_area_alloc_pages() * [PATCH v2 4/4] mm/vmalloc: cleanup gfp flag use in new_vmap_block() and found the following issue: WARNING: kmalloc bug in bpf_prog_alloc_no_stats Full report is available here: https://ci.syzbot.org/series/46d6cb1a-188d-4ff5-8fab-9c58465d74d3 *** WARNING: kmalloc bug in bpf_prog_alloc_no_stats tree: linux-next URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next base: b179ce312bafcb8c68dc718e015aee79b7939ff0 arch: amd64 compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 config: https://ci.syzbot.org/builds/3449e2a5-35e0-4eac-86c6-97ca0ec741d7/config ------------[ 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, CPU#1: syz-executor/6079 Modules linked in: CPU: 1 UID: 0 PID: 6079 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:vmalloc_fix_flags+0x9c/0xe0 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 40 c3 76 8b 4c 89 fa 89 d9 4d 89 f0 e8 a5 a1 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:ffffc90005557b00 EFLAGS: 00010246 RAX: a6bff5ae8e950700 RBX: 0000000000000dc0 RCX: ffff888173b29d40 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002 RBP: ffffc90005557b98 R08: 0000000000000003 R09: 0000000000000004 R10: dffffc0000000000 R11: fffffbfff1bba6ec R12: 1ffff92000aaaf60 R13: dffffc0000000000 R14: ffffc90005557b20 R15: ffffc90005557b30 FS: 000055557c070500(0000) GS:ffff8882a9ec0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f86f6df0000 CR3: 0000000113d64000 CR4: 00000000000006f0 Call Trace: __vmalloc_noprof+0xf2/0x120 bpf_prog_alloc_no_stats+0x4a/0x4d0 bpf_prog_alloc+0x3c/0x1a0 bpf_prog_create_from_user+0xa7/0x440 do_seccomp+0x7b1/0xd90 __se_sys_prctl+0xc3c/0x1830 do_syscall_64+0xfa/0xfa0 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fcbe2f90b0d 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:00007ffed4000b80 EFLAGS: 00000246 ORIG_RAX: 000000000000009d RAX: ffffffffffffffda RBX: 00007fcbe302cf80 RCX: 00007fcbe2f90b0d RDX: 00007ffed4000be0 RSI: 0000000000000002 RDI: 0000000000000016 RBP: 00007ffed4000bf0 R08: 0000000000000006 R09: 0000000000000071 R10: 0000000000000071 R11: 0000000000000246 R12: 000000000000006d R13: 00007ffed4001018 R14: 00007ffed4001298 R15: 0000000000000000 *** If these findings have caused you to resend the series or submit a separate fix, please add the following tag to your commit message: Tested-by: syzbot@syzkaller.appspotmail.com --- This report is generated by a bot. It may contain errors. syzbot ci engineers can be reached at syzkaller@googlegroups.com.