[moderation/CI] Re: bpf: Fix use-after-free on mm_struct in bpf_find_vma()

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

syzbot ci has tested the following series

[v5] bpf: Fix use-after-free on mm_struct in bpf_find_vma()
https://lore.kernel.org/all/20260630023443.3026627-2-sanghyun.park.cnu@gmail.com
* [PATCH bpf-next v5] bpf: Fix use-after-free on mm_struct in bpf_find_vma()

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/f0ce67c9-2c09-418c-bbe2-c698246e9c7f

***

kernel build error

tree:      bpf-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base:      53435562a725962e4de0c29653223129ba11643a
arch:      amd64
compiler:  Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config:    https://ci.syzbot.org/builds/a434cf48-2810-46a3-bb75-064be88b96be/config

kernel/bpf/task_iter.c:1017:3: error: call to undeclared function 'bpf_iter_mmput_async'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]

***

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:
[andrii@kernel.org ast@kernel.org bpf@vger.kernel.org daniel@iogearbox.net eddyz87@gmail.com emil@etsalapatis.com haoluo@google.com john.fastabend@gmail.com jolsa@kernel.org kpsingh@kernel.org linux-kernel@vger.kernel.org martin.lau@linux.dev memxor@gmail.com puranjay@kernel.org sanghyun.park.cnu@gmail.com sdf@fomichev.me song@kernel.org yonghong.song@linux.dev]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid