From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f71.google.com (mail-oo1-f71.google.com [209.85.161.71]) (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 CD4E423EAA3 for ; Sat, 11 Apr 2026 01:36:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.71 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775871403; cv=none; b=DoUur6r4PVgQa8eGOjM/KHbAaUV1m3h8rIAfgLRZwytvLwHr86qqjk3JIonW/wfPB4icxp4q8GGnrmmw0pTw1JdfaMI+QKz+pkF8pKHc++Y5xRRf11V0mmOnMbqWfWhrZh8tVB10w3ZngWORhIrT1XrwbC21QDK8RUImwIwjcVQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775871403; c=relaxed/simple; bh=gVL6XcTluJIGhE6N4mitfmDibslb6StW5FR3Za36fbI=; h=MIME-Version:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=dEaG4Q73jaaOhiYtSQ/XYXSuRRPQjhF0MQgJG2hPFvBdkABi4BpC1+Gg07gT7QN56f5Z6IdanOS/Vh4doZhC6dMw7Z8PvUYLDixi/zA0GoV5Bly4iw3lptWUHhPx53n43Lnis2BPpLzXSLhPK9NQj22FjxrmZpEW/nY9vuBDL14= 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.161.71 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-oo1-f71.google.com with SMTP id 006d021491bc7-672c40f3873so7127282eaf.2 for ; Fri, 10 Apr 2026 18:36:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1775871401; x=1776476201; h=cc:to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=s5DRL8R3CfffneTn7EsuWcj63P8TmdW0mMagFk+rVSM=; b=J9tQE6ZluKTwBCMofhOAlce/F1zBihgD95s8pudo8N2v41Cd7fll9lmFCb518lfQUi jM4ATj7dl+65X6C5pvqooSgvSK65Rwpoi34YoycDWIYKdjO9H0nsK+o1FLypLzc2gs0p 5+j9JGlu0/7GQM3H7gfodaNdfvatgi3EFAuv/F+P9x+lIPFknMjJelV32njtOWFh/N/M HgCHXRamELYAxBkbEu9vwyfCl/+IPFAvfoyBWgnovO2gmebHzs0N4/Z7TctHiLgpSaXu xNhAkTxw2cDS8kJ6JBEc2p0pFn5+V+XNlKzgKDKHZWKZ2LXYO2meoTap6J1QHX+MX9WR rcVA== X-Gm-Message-State: AOJu0Yw7mtjTHpDnul+Nh6O4TLv34YGhhpCDoB1ua1TjhXbMreVQdInd EgWaUYOErv6wp7tiBqGINhseufxUxfmgJPWR2b2ZQI6tEQ2RLQiolnlGm3mSC4jdlFNOafnYpHT /5+nwB7CY6gvzQwdrVRYTfsUDdLR8wKgHPFStSZ7aYPlLEKTF0aeuhQVKwps= Precedence: bulk X-Mailing-List: syzbot@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:81cd:b0:67e:3985:e110 with SMTP id 006d021491bc7-68be8dd0d21mr2571725eaf.56.1775871400840; Fri, 10 Apr 2026 18:36:40 -0700 (PDT) Date: Fri, 10 Apr 2026 18:36:40 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69d9a5a8.a00a0220.475f0.0001.GAE@google.com> Subject: [moderation/CI] Re: Use kmalloc_nolock() universally in BPF local storage From: syzbot ci To: syzkaller-upstream-moderation@googlegroups.com Cc: syzbot@lists.linux.dev Content-Type: text/plain; charset="UTF-8" syzbot ci has tested the following series [v1] Use kmalloc_nolock() universally in BPF local storage https://lore.kernel.org/all/20260411001711.3418264-1-ameryhung@gmail.com * [PATCH bpf-next v1 1/3] selftests/bpf: Remove kmalloc tracing from local storage create bench * [PATCH bpf-next v1 2/3] bpf: Use kmalloc_nolock() universally in local storage * [PATCH bpf-next v1 3/3] bpf: Remove gfp_flags plumbing from bpf_local_storage_update() and found the following issue: kernel build error Full report is available here: https://ci.syzbot.org/series/d872f8f0-ea33-4c8f-9566-6252b91d3fdf *** kernel build error tree: bpf-next URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git base: 0eeb0094ba0321f0927806857b5f01c1577bc245 arch: amd64 compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8 config: https://ci.syzbot.org/builds/1218c84a-dd96-4c8e-ab57-0bcc056e0895/config net/core/bpf_sk_storage.c:140:57: error: too many arguments to function call, expected 4, have 5 net/core/bpf_sk_storage.c:205:59: error: too many arguments to function call, expected 3, have 4 *** 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. To test a patch for this bug, please reply with `#syz test` (should be on a separate line). The patch should be attached to the email. Note: arguments like custom git repos and branches are not supported. The email will later be sent to: [alexei.starovoitov@gmail.com ameryhung@gmail.com andrii@kernel.org bpf@vger.kernel.org daniel@iogearbox.net kernel-team@meta.com martin.lau@kernel.org memxor@gmail.com netdev@vger.kernel.org] If the report looks fine to you, reply with: #syz upstream If the report is a false positive, reply with #syz invalid