From: syzbot ci <syzbot+ci39f36c25f8e9b7ac@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm/memblock: Fix reserve_mem allocation overlapping KHO scratch regions
Date: Sun, 30 Nov 2025 04:46:49 -0800 [thread overview]
Message-ID: <692c3cb9.a70a0220.d98e3.0171.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] mm/memblock: Fix reserve_mem allocation overlapping KHO scratch regions
https://lore.kernel.org/all/20251130172939.574999-1-swarajgaikwad1925@gmail.com
* [PATCH RFC] mm/memblock: Fix reserve_mem allocation overlapping KHO scratch regions
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/2063e5cf-1386-4258-a5f2-b62263550a7b
***
kernel build error
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 8ad78d36c2877966b6a5507987ae072b5b8456c0
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/89c1614d-75f5-4cd6-82fc-b13b1759edfa/config
mm/memblock.c:2692:18: error: use of undeclared identifier 'kho_scratch_cnt'
mm/memblock.c:2693:19: error: use of undeclared identifier 'kho_scratch'
mm/memblock.c:2694:17: error: use of undeclared identifier 'kho_scratch'
mm/memblock.c:2694:39: error: use of undeclared identifier 'kho_scratch'
***
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.
The email will later be sent to:
[akpm@linux-foundation.org david.hunter.linux@gmail.com linux-kernel@vger.kernel.org linux-mm@kvack.org rppt@kernel.org skhan@linuxfoundation.org swarajgaikwad1925@gmail.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-11-30 12: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=692c3cb9.a70a0220.d98e3.0171.GAE@google.com \
--to=syzbot+ci39f36c25f8e9b7ac@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