* [moderation/CI] Re: mm/ksm: clean up scan_get_next_rmap_item() initialization
@ 2026-11-19 4:57 syzbot ci
2026-11-19 6:57 ` Aleksandr Nogikh
0 siblings, 1 reply; 2+ messages in thread
From: syzbot ci @ 2026-11-19 4:57 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
syzbot ci has tested the following series
[v2] mm/ksm: clean up scan_get_next_rmap_item() initialization
https://lore.kernel.org/all/20261115075832.132109-1-xu.xin@linux.dev
* [PATCH v2 1/2] mm/ksm: extract helper functions for scan cycle cleanup
* [PATCH v2 2/2] mm/ksm: add initialization helpers for scan_get_next_rmap_item()
and found the following issue:
general protection fault in ksm_do_scan
Full report is available here:
https://ci.syzbot.org/series/cc51d824-2b5d-4c6d-bd56-c5bdb2bf5e12
***
general protection fault in ksm_do_scan
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 3dfc09a9493ddaa5e7722a29165d8450b55b4d3f
arch: amd64
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/6f9c12e2-f68e-40ee-bbac-84e33b709dfb/config
AI triage: https://ci.syzbot.org/findings/02a8022e-9e9a-4596-8a04-b8c4338b7e82/triage_trajectory
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000004: 0000 [#1] SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000020-0x0000000000000027]
CPU: 1 UID: 0 PID: 44 Comm: ksmd Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:ksm_do_scan+0x5da/0x6f40
Code: c7 05 86 a2 b1 19 00 00 00 00 48 8d 43 28 48 89 05 9b a2 b1 19 48 89 4c 24 40 48 8d 59 20 48 89 d8 48 c1 e8 03 48 89 44 24 78 <42> 80 3c 28 00 74 08 48 89 df e8 47 3a 01 00 48 89 5c 24 30 48 8b
RSP: 0018:ffffc90000b47a60 EFLAGS: 00010202
RAX: 0000000000000004 RBX: 0000000000000020 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffc90000b47c08
RBP: ffffc90000b47cd0 R08: ffffc90000b47c07 R09: 0000000000000000
R10: ffffc90000b47bb0 R11: fffff52000168f81 R12: 1ffff92000168f68
R13: dffffc0000000000 R14: ffffea00046aca00 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8882a77fd000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f15aa3f8c38 CR3: 0000000170aa2000 CR4: 00000000000006f0
Call Trace:
<TASK>
ksm_scan_thread+0x114/0x520
kthread+0x38b/0x480
ret_from_fork+0x514/0xb70
ret_from_fork_asm+0x1a/0x30
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ksm_do_scan+0x5da/0x6f40
Code: c7 05 86 a2 b1 19 00 00 00 00 48 8d 43 28 48 89 05 9b a2 b1 19 48 89 4c 24 40 48 8d 59 20 48 89 d8 48 c1 e8 03 48 89 44 24 78 <42> 80 3c 28 00 74 08 48 89 df e8 47 3a 01 00 48 89 5c 24 30 48 8b
RSP: 0018:ffffc90000b47a60 EFLAGS: 00010202
RAX: 0000000000000004 RBX: 0000000000000020 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffc90000b47c08
RBP: ffffc90000b47cd0 R08: ffffc90000b47c07 R09: 0000000000000000
R10: ffffc90000b47bb0 R11: fffff52000168f81 R12: 1ffff92000168f68
R13: dffffc0000000000 R14: ffffea00046aca00 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff88818bdfd000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c27b575 CR3: 000000010233e000 CR4: 00000000000006f0
***
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:
[chengming.zhou@linux.dev david@kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org ljs@kernel.org xu.xin@linux.dev]
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: mm/ksm: clean up scan_get_next_rmap_item() initialization
2026-11-19 4:57 [moderation/CI] Re: mm/ksm: clean up scan_get_next_rmap_item() initialization syzbot ci
@ 2026-11-19 6:57 ` Aleksandr Nogikh
0 siblings, 0 replies; 2+ messages in thread
From: Aleksandr Nogikh @ 2026-11-19 6:57 UTC (permalink / raw)
To: syzbot ci; +Cc: syzkaller-upstream-moderation, syzbot
#syz upstream
On Thu, Nov 19, 2026 at 5:57 AM syzbot ci
<syzbot+ci6274869ebbf20d77@syzkaller.appspotmail.com> wrote:
>
> syzbot ci has tested the following series
>
> [v2] mm/ksm: clean up scan_get_next_rmap_item() initialization
> https://lore.kernel.org/all/20261115075832.132109-1-xu.xin@linux.dev
> * [PATCH v2 1/2] mm/ksm: extract helper functions for scan cycle cleanup
> * [PATCH v2 2/2] mm/ksm: add initialization helpers for scan_get_next_rmap_item()
>
> and found the following issue:
> general protection fault in ksm_do_scan
>
> Full report is available here:
> https://ci.syzbot.org/series/cc51d824-2b5d-4c6d-bd56-c5bdb2bf5e12
>
> ***
>
> general protection fault in ksm_do_scan
>
> tree: mm-new
> URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
> base: 3dfc09a9493ddaa5e7722a29165d8450b55b4d3f
> arch: amd64
> compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
> config: https://ci.syzbot.org/builds/6f9c12e2-f68e-40ee-bbac-84e33b709dfb/config
> AI triage: https://ci.syzbot.org/findings/02a8022e-9e9a-4596-8a04-b8c4338b7e82/triage_trajectory
>
> Oops: general protection fault, probably for non-canonical address 0xdffffc0000000004: 0000 [#1] SMP KASAN PTI
> KASAN: null-ptr-deref in range [0x0000000000000020-0x0000000000000027]
> CPU: 1 UID: 0 PID: 44 Comm: ksmd Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> RIP: 0010:ksm_do_scan+0x5da/0x6f40
> Code: c7 05 86 a2 b1 19 00 00 00 00 48 8d 43 28 48 89 05 9b a2 b1 19 48 89 4c 24 40 48 8d 59 20 48 89 d8 48 c1 e8 03 48 89 44 24 78 <42> 80 3c 28 00 74 08 48 89 df e8 47 3a 01 00 48 89 5c 24 30 48 8b
> RSP: 0018:ffffc90000b47a60 EFLAGS: 00010202
> RAX: 0000000000000004 RBX: 0000000000000020 RCX: 0000000000000000
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffc90000b47c08
> RBP: ffffc90000b47cd0 R08: ffffc90000b47c07 R09: 0000000000000000
> R10: ffffc90000b47bb0 R11: fffff52000168f81 R12: 1ffff92000168f68
> R13: dffffc0000000000 R14: ffffea00046aca00 R15: 0000000000000000
> FS: 0000000000000000(0000) GS:ffff8882a77fd000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f15aa3f8c38 CR3: 0000000170aa2000 CR4: 00000000000006f0
> Call Trace:
> <TASK>
> ksm_scan_thread+0x114/0x520
> kthread+0x38b/0x480
> ret_from_fork+0x514/0xb70
> ret_from_fork_asm+0x1a/0x30
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:ksm_do_scan+0x5da/0x6f40
> Code: c7 05 86 a2 b1 19 00 00 00 00 48 8d 43 28 48 89 05 9b a2 b1 19 48 89 4c 24 40 48 8d 59 20 48 89 d8 48 c1 e8 03 48 89 44 24 78 <42> 80 3c 28 00 74 08 48 89 df e8 47 3a 01 00 48 89 5c 24 30 48 8b
> RSP: 0018:ffffc90000b47a60 EFLAGS: 00010202
> RAX: 0000000000000004 RBX: 0000000000000020 RCX: 0000000000000000
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffc90000b47c08
> RBP: ffffc90000b47cd0 R08: ffffc90000b47c07 R09: 0000000000000000
> R10: ffffc90000b47bb0 R11: fffff52000168f81 R12: 1ffff92000168f68
> R13: dffffc0000000000 R14: ffffea00046aca00 R15: 0000000000000000
> FS: 0000000000000000(0000) GS:ffff88818bdfd000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 000000110c27b575 CR3: 000000010233e000 CR4: 00000000000006f0
>
>
> ***
>
> 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:
> [chengming.zhou@linux.dev david@kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org ljs@kernel.org xu.xin@linux.dev]
>
> 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/6afe81b2.902182b0.170f33.0002.GAE%40google.com.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-11-19 6:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-19 4:57 [moderation/CI] Re: mm/ksm: clean up scan_get_next_rmap_item() initialization syzbot ci
2026-11-19 6:57 ` 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.