[moderation/CI] Re: Use kmalloc_nolock() universally in BPF local storage

[syzbot ci <syzbot+ci6627230c9266a656@syzkaller.appspotmail.com>]

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