Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci96bfa5a8ff3778dd@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm: introduce ANON_VMA_LAZY for deferred anon_vma creation
Date: Wed, 27 May 2026 13:44:05 -0700	[thread overview]
Message-ID: <6a175795.52c88913.99dcf.0000.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] mm: introduce ANON_VMA_LAZY for deferred anon_vma creation
https://lore.kernel.org/all/20260527110147.17815-1-tao.wangtao@honor.com
* [PATCH 01/15] mm/rmap: introduce anon_rmap APIs for anonymous folios
* [PATCH 02/15] mm: convert anon_vma rmap APIs to anon_rmap
* [PATCH 03/15] mm: introduce anon_vma_tree_t for multiple anon_vma topologies
* [PATCH 04/15] mm: switch to anon_vma_tree_t APIs in preparation for ANON_VMA_LAZY
* [PATCH 05/15] mm: add CONFIG_ANON_VMA_LAZY and folio helpers
* [PATCH 06/15] mm: add CONFIG_VMA_REF and VMA helpers
* [PATCH 07/15] mm: replace direct FOLIO_MAPPING_ANON usage with helpers
* [PATCH 08/15] mm: prepare rmap infrastructure for ANON_VMA_LAZY
* [PATCH 09/15] mm: implement ANON_VMA_LAZY rmap semantics
* [PATCH 10/15] mm: defer anon_vma creation with ANON_VMA_LAZY
* [PATCH 11/15] mm: handle ANON_VMA_LAZY in huge page operations
* [PATCH 12/15] mm: handle ANON_VMA_LAZY during migration
* [PATCH 13/15] mm: support setup and upgrade of ANON_VMA_LAZY folios
* [PATCH 14/15] mm: support merging of ANON_VMA_LAZY VMAs
* [PATCH 15/15] mm: enable CONFIG_ANON_VMA_LAZY on arm64 and x86_64

and found the following issue:
SYZFATAL: image testing failed w/o kernel bug

Full report is available here:
https://ci.syzbot.org/series/c401d17b-0a67-4742-b7dc-c49a853a31dd

***

SYZFATAL: image testing failed w/o kernel bug

tree:      mm-new
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base:      e8c2f9fdadee7cbc75134dc463c1e0d856d6e5c7
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/69c9ca24-ff3b-4eb2-92f8-347468dba382/config



***

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:
[21cnbao@gmail.com akpm@linux-foundation.org apopple@nvidia.com baohua@kernel.org baolin.wang@linux.alibaba.com bp@alien8.de byungchul@sk.com catalin.marinas@arm.com chengming.zhou@linux.dev damon@lists.linux.dev dave.hansen@linux.intel.com david@kernel.org dev.jain@arm.com dvander@google.com gourry@gourry.net harry@kernel.org hpa@zytor.com jack@suse.cz jannh@google.com jgg@ziepe.ca jhubbard@nvidia.com joshua.hahnjy@gmail.com jparsana@google.com kas@kernel.org kees@kernel.org lance.yang@linux.dev liam@infradead.org linux-arm-kernel@lists.infradead.org linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org ljs@kernel.org luizcap@redhat.com matthew.brost@intel.com mhocko@suse.com mingo@redhat.com nao.horiguchi@gmail.com npache@redhat.com peterx@redhat.com pfalcato@suse.de rakie.kim@sk.com riel@surriel.com rppt@kernel.org ryan.roberts@arm.com ryncsn@gmail.com shakeel.butt@linux.dev sj@kernel.org surenb@google.com tao.wangtao@honor.com tglx@kernel.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-05-27 20:44 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=6a175795.52c88913.99dcf.0000.GAE@google.com \
    --to=syzbot+ci96bfa5a8ff3778dd@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