All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci9bad7a2874253ab4@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm: migrate: transfer large_rmappable flag in folio_migrate_flags()
Date: Wed, 11 Mar 2026 20:53:34 -0700	[thread overview]
Message-ID: <69b238be.a00a0220.94e15.001f.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] mm: migrate: transfer large_rmappable flag in folio_migrate_flags()
https://lore.kernel.org/all/20260311132342.3193160-1-usama.arif@linux.dev
* [PATCH] mm: migrate: transfer large_rmappable flag in folio_migrate_flags()

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

Full report is available here:
https://ci.syzbot.org/series/67700b4e-141e-41a3-a846-874bb5239e01

***

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:      f543926f9d0c3f6dfb354adfe7fbaeedd1277c6b
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/ee937fd7-0b18-4438-8575-85af5c8a9267/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.

The email will later be sent to:
[akpm@linux-foundation.org apopple@nvidia.com byungchul@sk.com david@kernel.org gourry@gourry.net hannes@cmpxchg.org joshua.hahnjy@gmail.com kernel-team@meta.com linux-kernel@vger.kernel.org linux-mm@kvack.org matthew.brost@intel.com npache@redhat.com rakie.kim@sk.com usama.arif@linux.dev willy@infradead.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-03-12  3:53 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=69b238be.a00a0220.94e15.001f.GAE@google.com \
    --to=syzbot+ci9bad7a2874253ab4@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.