From: syzbot ci <syzbot+ci32ea311716440601@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: userfaultfd: assorted fixes (part 1)
Date: Fri, 20 Nov 2026 02:47:01 -0800 [thread overview]
Message-ID: <6b002525.a159c4fa.1dac72.000e.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] userfaultfd: assorted fixes (part 1)
https://lore.kernel.org/all/20261116-uffd-state-fixes-v2-0-4397a0196479@columbia.edu
* [PATCH v2 1/9] userfaultfd: use anonymous memory for UFFDIO_ZEROPAGE on private file mappings
* [PATCH v2 2/9] userfaultfd: refuse UFFDIO_MOVE into a non-present huge destination PMD
* [PATCH v2 3/9] fs/proc/task_mmu: downgrade writable migration entries in PAGEMAP_SCAN write-protect
* [PATCH v2 4/9] mm/migrate: keep the uffd bit when restoring a writable migration entry
* [PATCH v2 5/9] fs/proc/task_mmu: write-protect device-private THPs in PAGEMAP_SCAN
* [PATCH v2 6/9] mm/huge_memory: build the moved huge zero PMD from the destination VMA
* [PATCH v2 7/9] mm/mremap: resolve uffd state when the context is dropped, not during the move
* [PATCH v2 8/9] mm/migrate_device: do not migrate a uffd-protected zero page
* [PATCH v2 9/9] mm/userfaultfd: check hugetlb end alignment in UFFDIO_UNREGISTER pre-scan
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/df454fee-723d-460c-b690-eed0efd62886
***
kernel build error
tree: drm-next
URL: https://gitlab.freedesktop.org/drm/kernel.git
base: 601c30449c80926947d4820d50cec974687d1d11
arch: amd64
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/660c1e39-c2f3-4ef1-8213-53c924b66a8c/config
mm/userfaultfd.c:3145:3: error: call to undeclared function 'userfaultfd_clear_ptes'; 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.
The email will later be sent to:
[aarcange@redhat.com akpm@linux-foundation.org amd-gfx@lists.freedesktop.org apopple@nvidia.com arnd@arndb.de avagin@gmail.com balbirs@nvidia.com baohua@kernel.org baolin.wang@linux.alibaba.com byungchul@sk.com dakr@kernel.org david@kernel.org dev.jain@arm.com dri-devel@lists.freedesktop.org felix.kuehling@amd.com gourry@gourry.net intel-xe@lists.freedesktop.org jannh@google.com jgg@ziepe.ca joshua.hahnjy@gmail.com jthoughton@google.com kas@kernel.org lance.yang@linux.dev leitao@debian.org leon@kernel.org liam@infradead.org linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org ljs@kernel.org lyude@redhat.com matthew.brost@intel.com mhocko@suse.com miko.lenczewski@arm.com mirq-linux@rere.qmqm.pl muchun.song@linux.dev nico.pache@linux.dev nouveau@lists.freedesktop.org osalvador@suse.de peterx@redhat.com pfalcato@suse.de rppt@kernel.org ryan.roberts@arm.com sfr@canb.auug.org.au stable@vger.kernel.org surenb@google.com thomas.hellstrom@linux.intel.com tz2294@columbia.edu usama.anjum@arm.com usama.arif@linux.dev vbabka@kernel.org ying.huang@linux.alibaba.com 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-11-20 10:47 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=6b002525.a159c4fa.1dac72.000e.GAE@google.com \
--to=syzbot+ci32ea311716440601@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.