From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-il1-f200.google.com (mail-il1-f200.google.com [209.85.166.200]) (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 F3413262FF8 for ; Tue, 18 Nov 2025 08:46:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.166.200 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763455576; cv=none; b=Y0kZd7zIcEt1QmbibJezs0NbchoOeX0ZoVFSXnRnnrx6SaX1zexkQDiwaLPsJNj1ephG47uzz+qaUeoFnXGickQlVYfgbQhdi0wUEuFgH+Qz5/ntMwI+9lp6Uu+mbwlavvFspU71kuirvmg4Ay1cVuOu+LBf1T4NIgPNiNbeAIE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763455576; c=relaxed/simple; bh=9Cpk1ZNWkSr+zG+oMoUwV6ks1dJjeLtvy5JfsdpcSFc=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To:Cc: Content-Type; b=qvoF7mUwQ71dfU1kx72EW8ZI+v5vtbtJw0HFHKM9rQAjAkjzN6pvQ4xutEFkxce60GKZkm30W/aD7xAJC7ha2ZpRoca880aim91k1OnJkLeA+9/j5RgQBqwGaqOCsf2wU9xSQW8n+TFcBudTxBo6+PwQ6a0N3EdtpQpvhXd5Qq8= 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.200 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-f200.google.com with SMTP id e9e14a558f8ab-43329b607e0so59408195ab.2 for ; Tue, 18 Nov 2025 00:46:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763455574; x=1764060374; 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=gRIBR7nKyt0lzCZDU7BoFwtHeQyo2pGhv6COg15G0gU=; b=AVJTmqcI8AzPXg7Y4KEG/s6tc4r58s2C2wDkP9bH3jx+yEb0ujiN6QAPHY3YQmWWKY fWv9KJEZ1lc6oUSKVf691cnK747EIE8E/yvum3c4rdChgMo+JtFGKnKBFE774PMZnF5z 3ccejlYjfQ6rgjc/C+fe8GGR4yVQ2RAHoo/GwOXsGOoLi1GUgho2v5KmkmbtTAnmM0+K qtX3W0U4x+ldfTaXY3glQYfjvImJeKSWTxzR/cqkTWTrOfxphipUd3SYgSfTZ6GT5tjf 1V1e1UgRQ21QBTwvptsuBS42Jq6D1Vv4a098O/rCBZFm6N3uBWRdyclIceZACj2J343U cVbQ== X-Forwarded-Encrypted: i=1; AJvYcCUIH+2FvXm1+5Em5dBnm59rJVd6o6ozcMZWM85cfflIQhSa/WTh1zsRfiQmvRd2oHEj6Jx1JB+gq0Dv65U=@vger.kernel.org X-Gm-Message-State: AOJu0YxYkVT38BKJILx6OomSGrYYmwiiCRrtP0UNnnZ+jQdwK3C5nuDU 0VKHmSoGzavx5VmODrVuh79+zH8Pp9VElUUXv+2d+kdL+ld8C21FoDm34LWv5YeRC/BByYUL9+O FLKsTH9/ClFkS8SvWp6cyfh4L+U4VGGhm7Kcyk5x0uzWWQtCI8bi3pna2yXQ= X-Google-Smtp-Source: AGHT+IH1E+VLDYIvY3O0hSevd7z7LwPjZPul6wO2Yab5t2z9KIJZhyauwcLSrmMyLZHPIDK6aVt2fFg3D4gWyhBIYHNum4R38hnT 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:8a:b0:433:7d04:55da with SMTP id e9e14a558f8ab-4348c93ebf0mr201382765ab.31.1763455574118; Tue, 18 Nov 2025 00:46:14 -0800 (PST) Date: Tue, 18 Nov 2025 00:46:14 -0800 In-Reply-To: <20251117224701.1279139-1-ackerleytng@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <691c3256.a70a0220.3124cb.00b6.GAE@google.com> Subject: [syzbot ci] Re: Extend xas_split* to support splitting arbitrarily large entries From: syzbot ci To: ackerleytng@google.com, akpm@linux-foundation.org, david@redhat.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, michael.roth@amd.com, vannapurve@google.com, willy@infradead.org Cc: syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" syzbot ci has tested the following series [v1] Extend xas_split* to support splitting arbitrarily large entries https://lore.kernel.org/all/20251117224701.1279139-1-ackerleytng@google.com * [RFC PATCH 1/4] XArray: Initialize nodes while splitting instead of while allocating * [RFC PATCH 2/4] XArray: Update xas_split_alloc() to allocate enough nodes to split large entries * [RFC PATCH 3/4] XArray: Support splitting for arbitrarily large entries * [RFC PATCH 4/4] XArray: test: Increase split order test range in check_split() and found the following issue: WARNING: kmalloc bug in bpf_prog_alloc_no_stats Full report is available here: https://ci.syzbot.org/series/aa74d39d-0773-4398-bb90-0a6d21365c3d *** WARNING: kmalloc bug in bpf_prog_alloc_no_stats tree: mm-new URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git base: 41218ede767f6b218185af65ce919d0cade75f6b 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/c26972f6-b81e-4d6f-bead-3d77003cf075/config ------------[ cut here ]------------ Unexpected gfp: 0x400000 (__GFP_ACCOUNT). Fixing up to gfp: 0xdc0 (GFP_KERNEL|__GFP_ZERO). Fix your code! WARNING: CPU: 0 PID: 6465 at mm/vmalloc.c:3938 vmalloc_fix_flags+0x9c/0xe0 Modules linked in: CPU: 0 UID: 0 PID: 6465 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 c0 b9 76 8b 4c 89 fa 89 d9 4d 89 f0 e8 75 2b 6e 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:ffffc90005d7fb00 EFLAGS: 00010246 RAX: 6e85c22fb4362300 RBX: 0000000000000dc0 RCX: ffff888176898000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002 RBP: ffffc90005d7fb98 R08: ffff888121224293 R09: 1ffff11024244852 R10: dffffc0000000000 R11: ffffed1024244853 R12: 1ffff92000baff60 R13: dffffc0000000000 R14: ffffc90005d7fb20 R15: ffffc90005d7fb30 FS: 000055555be14500(0000) GS:ffff88818eb36000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f653e85c470 CR3: 00000001139ec000 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:0x7f653e990b0d 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:00007fffbd3687c0 EFLAGS: 00000246 ORIG_RAX: 000000000000009d RAX: ffffffffffffffda RBX: 00007f653ea2cf80 RCX: 00007f653e990b0d RDX: 00007fffbd368820 RSI: 0000000000000002 RDI: 0000000000000016 RBP: 00007fffbd368830 R08: 0000000000000006 R09: 0000000000000071 R10: 0000000000000071 R11: 0000000000000246 R12: 000000000000006d R13: 00007fffbd368c58 R14: 00007fffbd368ed8 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.