All of lore.kernel.org
 help / color / mirror / Atom feed
* [moderation/CI] Re: migrate on fault for device pages
@ 2026-09-26 15:00 syzbot ci
  2026-09-26 20:51 ` Aleksandr Nogikh
  0 siblings, 1 reply; 2+ messages in thread
From: syzbot ci @ 2026-09-26 15:00 UTC (permalink / raw)
  To: syzkaller-upstream-moderation; +Cc: syzbot

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [moderation/CI] Re: migrate on fault for device pages
  2026-09-26 15:00 [moderation/CI] Re: migrate on fault for device pages syzbot ci
@ 2026-09-26 20:51 ` Aleksandr Nogikh
  0 siblings, 0 replies; 2+ messages in thread
From: Aleksandr Nogikh @ 2026-09-26 20:51 UTC (permalink / raw)
  To: syzbot ci; +Cc: syzkaller-upstream-moderation, syzbot

#syz invalid

On Sat, Sep 26, 2026 at 11:00 AM syzbot ci
<syzbot+ci8e1d2d3902f1476b@syzkaller.appspotmail.com> wrote:
>
> 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
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-moderation+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/6ab7de1a.e548f532.1ca396.002e.GAE%40google.com.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-09-26 20:52 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-09-26 15:00 [moderation/CI] Re: migrate on fault for device pages syzbot ci
2026-09-26 20:51 ` Aleksandr Nogikh

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.