[moderation/CI] Re: bpf, verifier: fix PTR_TO_FLOW_KEYS constant-offset OOB
syzbot ci <[email protected]>
| Newsgroups | dev.linux.lists.syzbot |
|---|---|
| Message-ID | <[email protected]> |
syzbot ci has tested the following series [v2] bpf, verifier: fix PTR_TO_FLOW_KEYS constant-offset OOB https://lore.kernel.org/all/[email protected] * [PATCH bpf-next v2 1/2] bpf, verifier: fold reg->var_off into PTR_TO_FLOW_KEYS bounds check * [PATCH bpf-next v2 2/2] selftests/bpf: add tests for PTR_TO_FLOW_KEYS constant offset bounds and found the following issue: kernel build error Full report is available here: https://ci.syzbot.org/series/a021d8ae-94c2-49bf-8d77-3c89bcf82592 *** kernel build error tree: bpf-next URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git base: 8a7f2bff2165e53595d1e91c160b340f978c0ab7 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/251e72d5-7f60-4e2a-a290-d22661def7ef/config kernel/bpf/verifier.c:6255:37: error: use of undeclared identifier 'regno' *** 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: [email protected] --- This report is generated by a bot. It may contain errors. syzbot ci engineers can be reached at [email protected]. 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: [[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]] If the report looks fine to you, reply with: #syz upstream If the report is a false positive, reply with #syz invalid