From: syzbot ci <syzbot+cic1dcc0d9b21712a7@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm: introduce __ptent sparse attribute
Date: Fri, 17 Jul 2026 14:19:14 -0700 [thread overview]
Message-ID: <6a5a9c52.f1649fcc.2a4208.0253.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] mm: introduce __ptent sparse attribute
https://lore.kernel.org/all/cover.1784292223.git.agordeev@linux.ibm.com
* [RFC PATCH 1/4] mm: use proper PTE accessors in madvise() and mremap()
* [RFC PATCH 2/4] mm: introduce ptep_get_nopgtable() and set_pte_nopgtable() accessors
* [RFC PATCH 3/4] mm: introduce __ptent sparse attribute
* [RFC PATCH 4/4] s390/mm: implement __ptent-aware pte_t type
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/62b04622-8836-4d29-9a8a-0f9a1110d500
***
kernel build error
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: c3330b3115e013ea8160338e5d8b32a1fff26173
arch: amd64
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config: https://ci.syzbot.org/builds/938e6a38-5507-4c5c-a6db-514b6c9a59e1/config
./include/linux/pgtable.h:500:38: error: call to undeclared function 'PageTable'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
./include/linux/pgtable.h:512:38: error: call to undeclared function 'PageTable'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
***
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 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:
[agordeev@linux.ibm.com borntraeger@linux.ibm.com david@redhat.com gerald.schaefer@linux.ibm.com hca@linux.ibm.com imbrenda@linux.ibm.com kevin.brodsky@arm.com linux-kernel@vger.kernel.org linux-mm@kvack.org linux-s390@vger.kernel.org linux-sparse@vger.kernel.org sparse@chrisli.org]
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-07-17 21:19 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=6a5a9c52.f1649fcc.2a4208.0253.GAE@google.com \
--to=syzbot+cic1dcc0d9b21712a7@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