[moderation/CI] Re: improve per-node allocation and reclaim visibility

0 views
Skip to first unread message

syzbot ci

unread,
Feb 12, 2026, 1:00:05 PMFeb 12
to syzkaller-upst...@googlegroups.com, syz...@lists.linux.dev
syzbot ci has tested the following series

[v1] improve per-node allocation and reclaim visibility
https://lore.kernel.org/all/20260212045109.255...@gmail.com
* [PATCH 1/2] mm/mempolicy: track page allocations per mempolicy
* [PATCH 2/2] mm: move pgscan and pgsteal to node stats

and found the following issue:
WARNING in __mod_node_page_state

Full report is available here:
https://ci.syzbot.org/series/4ec12ede-3298-43a3-ab6b-79d47759672e

***

WARNING in __mod_node_page_state

tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 72a46cdd4ef13690beb8c5a2f6a2023fd7ef2eb4
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/0f678e4c-a4ba-4f17-8ed7-8ae99e56a463/config

------------[ cut here ]------------
IS_ENABLED(CONFIG_PREEMPT_COUNT) && __lockdep_enabled && (preempt_count() == 0 && this_cpu_read(hardirqs_enabled))
WARNING: mm/vmstat.c:396 at __mod_node_page_state+0x126/0x170, CPU#0: kthreadd/2
Modules linked in:
CPU: 0 UID: 0 PID: 2 Comm: kthreadd Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:__mod_node_page_state+0x126/0x170
Code: 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc 48 89 df 4c 89 e6 44 89 fa e8 68 00 00 00 31 db eb cc 90 0f 0b 90 e9 3e ff ff ff 90 <0f> 0b 90 eb 80 48 c7 c7 e0 c6 64 8e 4c 89 f6 e8 66 3c d3 02 e9 28
RSP: 0000:ffffc900000773d0 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000001 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 000000000000003d RDI: ffff88815fffb380
RBP: dffffc0000000000 R08: ffffffff8fef2977 R09: 1ffffffff1fde52e
R10: dffffc0000000000 R11: fffffbfff1fde52f R12: ffff88815fffb380
R13: ffffffff92f50f00 R14: 000000000000003d R15: 000000000000003d
FS: 0000000000000000(0000) GS:ffff88818e0f0000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000e346000 CR4: 00000000000006f0
Call Trace:
<TASK>
alloc_pages_mpol+0x407/0x740
alloc_pages_noprof+0xa8/0x190
get_free_pages_noprof+0xf/0x80
__kasan_populate_vmalloc+0x38/0x1d0
alloc_vmap_area+0xd21/0x1460
__get_vm_area_node+0x1f8/0x300
__vmalloc_node_range_noprof+0x372/0x1730
__vmalloc_node_noprof+0xc2/0x100
dup_task_struct+0x228/0x9a0
copy_process+0x508/0x3980
kernel_clone+0x248/0x870
kernel_thread+0x13f/0x1b0
kthreadd+0x4f9/0x6f0
ret_from_fork+0x51b/0xa40
ret_from_fork_asm+0x1a/0x30
</TASK>


***

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: syz...@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzk...@googlegroups.com.

The email will later be sent to:
[ak...@linux-foundation.org apo...@nvidia.com axelra...@google.com byun...@sk.com cgr...@vger.kernel.org da...@kernel.org eper...@redhat.com gou...@gourry.net han...@cmpxchg.org inward...@gmail.com jaso...@redhat.com joshua...@gmail.com kerne...@meta.com liam.h...@oracle.com linux-...@vger.kernel.org linu...@kvack.org lorenzo...@oracle.com matthe...@intel.com mho...@suse.com m...@redhat.com muchu...@linux.dev raki...@sk.com roman.g...@linux.dev rp...@kernel.org shakee...@linux.dev sur...@google.com vba...@suse.cz virtual...@lists.linux.dev wei...@google.com xuan...@linux.alibaba.com ying....@linux.alibaba.com yua...@google.com zhengq...@bytedance.com z...@nvidia.com]

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

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

Aleksandr Nogikh

unread,
Feb 12, 2026, 1:06:01 PMFeb 12
to syzbot ci, syzkaller-upst...@googlegroups.com, syz...@lists.linux.dev
#syz upstream
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/698e1521.a70a0220.2c38d7.009b.GAE%40google.com.
Reply all
Reply to author
Forward
0 new messages