All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci8e1d2d3902f1476b@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: migrate on fault for device pages
Date: Sat, 26 Sep 2026 08:00:42 -0700	[thread overview]
Message-ID: <6ab7de1a.e548f532.1ca396.002e.GAE@google.com> (raw)

syzbot ci has tested the following series

[v15] migrate on fault for device pages
https://lore.kernel.org/all/20260924065313.899730-1-mpenttil@redhat.com
* [PATCH v15 01/11] mm/Kconfig: changes for migrate on fault for device pages
* [PATCH v15 02/11] mm: add helper to convert HMM pfn to migrate pfn
* [PATCH v15 03/11] mm/hmm: preparations for HMM to participate in migration
* [PATCH v15 04/11] mm/hmm: do the plumbing for HMM to participate in migration
* [PATCH v15 05/11] mm/hmm: migrate collection in HMM pagewalk - pte level
* [PATCH v15 06/11] mm/hmm: migrate collection in HMM pagewalk - pmd level
* [PATCH v15 07/11] mm/hmm: add lazy MMU mode support for migration in HMM pagewalk
* [PATCH v15 08/11] mm/hmm: implement rollback for device page migration in HMM pagewalk
* [PATCH v15 09/11] mm: enable device page migration from HMM pagewalk
* [PATCH v15 10/11] lib/test_hmm: add a new testcase for the migrate on fault
* [PATCH v15 11/11] Documentation/mm/hmm: document migration through hmm_range_fault()

and found the following issue:
kernel panic: Fatal exception

Full report is available here:
https://ci.syzbot.org/series/e83269ed-df96-404f-95bb-3815267ab7b6

***

kernel panic: Fatal exception

tree:      drm-next
URL:       https://gitlab.freedesktop.org/drm/kernel.git
base:      2abe8e7e33973dda5dd24b89aa3ee52470a78265
arch:      amd64
compiler:  Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config:    https://ci.syzbot.org/builds/8d10dc50-efeb-4533-8f7a-d7fcf6b5a3b3/config
AI triage: https://ci.syzbot.org/findings/cf11d87e-9315-4738-a194-f8ccc16c2736/triage_trajectory

FS:  0000555594951500(0000) GS:ffff88818d6c2000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f384eb3aff8 CR3: 0000000171b40000 CR4: 00000000000006f0
Kernel panic - not syncing: Fatal exception
Kernel Offset: disabled
Rebooting in 86400 seconds..


***

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 fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.

Notes:
- The patch will be applied on top of the tested series (as an
  incremental fix).
- To test a new version of the whole series, please send it directly
  to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.

The email will later be sent to:
[akpm@linux-foundation.org apopple@nvidia.com balbirs@nvidia.com david@kernel.org dri-devel@lists.freedesktop.org intel-xe@lists.freedesktop.org jgg@nvidia.com leonro@nvidia.com liam.howlett@oracle.com linux-kernel@vger.kernel.org linux-mm@kvack.org ljs@kernel.org marpagan@redhat.com matthew.brost@intel.com mhocko@suse.com mpenttil@redhat.com rppt@kernel.org surenb@google.com vbabka@suse.cz 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-09-26 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26 15:00 syzbot ci [this message]
2026-09-26 20:51 ` [moderation/CI] Re: migrate on fault for device pages Aleksandr Nogikh

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=6ab7de1a.e548f532.1ca396.002e.GAE@google.com \
    --to=syzbot+ci8e1d2d3902f1476b@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.