public inbox for syzbot@lists.linux.dev
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci4bd68a8c659226a4@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm, KMSAN: Add missing shadow memory initialization in special allocation paths
Date: Mon, 30 Mar 2026 02:48:18 -0700	[thread overview]
Message-ID: <69ca46e2.050a0220.183828.0018.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] mm, KMSAN: Add missing shadow memory initialization in special allocation paths
https://lore.kernel.org/all/20260330-fix-kmsan-v1-1-e9c672a4b9eb@gmail.com
* [PATCH] mm, KMSAN: Add missing shadow memory initialization in special allocation paths

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/01b23d95-95d3-4352-a7f4-9df80f1c0dd8

***

kernel build error

tree:      drm-next
URL:       https://gitlab.freedesktop.org/drm/kernel.git
base:      bbeb83d3182abe0d245318e274e8531e5dd7a948
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/592f437a-4b31-47b4-8094-de233e42cd72/config

mm/page_alloc.c:7131:23: error: use of undeclared identifier 'page'
mm/page_alloc.c:7131:72: error: use of undeclared identifier 'page'
mm/page_alloc.c:7132:20: error: use of undeclared identifier 'page'

***

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 hannes@cmpxchg.org jackmanb@google.com jhubbard@nvidia.com ke.zhao.kernel@gmail.com linux-kernel@vger.kernel.org linux-mm@kvack.org mhocko@suse.com surenb@google.com syzbot@syzkaller.appspotmail.com vbabka@kernel.org ziy@nvidia.com]

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-03-30  9:48 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=69ca46e2.050a0220.183828.0018.GAE@google.com \
    --to=syzbot+ci4bd68a8c659226a4@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