From: syzbot ci <syzbot+ci6592343467b4698a@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: lib/folio_pool: Direct-Map Large Folio Pool & Scratchpad bump allocators
Date: Mon, 17 Aug 2026 11:46:13 -0700 [thread overview]
Message-ID: <6a8356f5.dbb3a75c.20434b.006d.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] lib/folio_pool: Direct-Map Large Folio Pool & Scratchpad bump allocators
https://lore.kernel.org/all/20260817-folio-pool-v1-v1-0-0c1d230aa3af@gmail.com
* [PATCH 1/9] lib/folio_pool: Introduce Direct-Map Large Folio Pool & Scratchpad bump allocators
* [PATCH 2/9] netfilter/nf_tables: Add folio_scratchpad collector to struct nftables_pernet
* [PATCH 3/9] bpf/verifier: Route verifier stack state node allocations to folio_pool
* [PATCH 4/9] drm/gpuvm: Route gpuva_op allocations to folio_scratchpad
* [PATCH 5/9] bpf/syscall: Route generic_map_update_batch key/value allocations to folio_scratchpad
* [PATCH 6/9] locking/lockdep: Fallback to folio_pool in alloc_list_entry when static pool is full
* [PATCH 7/9] locking/lockdep: Traverse adjacency lists directly in zap_class()
* [PATCH 8/9] locking/lockdep: Shrink static list_entries array to early bootstrap buffer
* [PATCH 9/9] locking/lockdep: Migrate and compact boot-time dependency graph from __initdata
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/0cb00027-e611-48c2-b3cf-f1fa17fa3ba2
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: e6a5d573d24cd375e09d24f136523cb3cc85c9d3
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/fee80397-36af-4dbf-9041-4ac6840fc40d/config
net/netfilter/nf_tables_api.c:12172:7: error: incompatible pointer types passing 'struct static_key_true *' to parameter of type 'struct static_key *' [-Wincompatible-pointer-types]
drivers/gpu/drm/drm_gpuvm.c:1113:8: error: use of undeclared identifier 'gpuvm_scratchpad_key'
kernel/bpf/syscall.c:2090:42: error: incompatible pointer types passing 'struct static_key_true *' to parameter of type 'struct static_key *' [-Wincompatible-pointer-types]
kernel/bpf/verifier.c:19799:27: error: incompatible pointer types passing 'struct static_key_true *' to parameter of type 'struct static_key *' [-Wincompatible-pointer-types]
***
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 fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[airlied@gmail.com akpm@linux-foundation.org aliceryhl@google.com andrii@kernel.org ast@kernel.org boqun@kernel.org boris.brezillon@collabora.com bpf@vger.kernel.org coreteam@netfilter.org dakr@kernel.org daniel@iogearbox.net davem@davemloft.net devnull@kernel.org dri-devel@lists.freedesktop.org eddyz87@gmail.com edumazet@google.com emil@etsalapatis.com fw@strlen.de horms@kernel.org jim.cromie@gmail.com john.fastabend@gmail.com jolsa@kernel.org kuba@kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org longman@redhat.com maarten.lankhorst@linux.intel.com martin.lau@linux.dev matthew.brost@intel.com memxor@gmail.com mingo@redhat.com mripard@kernel.org netdev@vger.kernel.org netfilter-devel@vger.kernel.org pabeni@redhat.com pablo@netfilter.org peterz@infradead.org phil@nwl.cc simona@ffwll.ch song@kernel.org thomas.hellstrom@linux.intel.com tzimmermann@suse.de will@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
reply other threads:[~2026-08-17 18:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a8356f5.dbb3a75c.20434b.006d.GAE@google.com \
--to=syzbot+ci6592343467b4698a@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).