From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: syzbot ci <syzbot+ci7e1f981ab411668d@syzkaller.appspotmail.com>
Cc: chengming.zhou@linux.dev, david@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
xu.xin@linux.dev, syzbot@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot ci] Re: mm/ksm: clean up scan_get_next_rmap_item() initialization
Date: Thu, 19 Nov 2026 11:34:58 +0000 [thread overview]
Message-ID: <av7e0B-1GCyk6sDs@gremlin> (raw)
In-Reply-To: <6afe9e8e.92f98041.20636d.0002.GAE@google.com>
On Wed, Nov 18, 2026 at 11:00:30PM -0800, syzbot ci 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
I guess it didn't see the v3? Likely this is the sashiko thing, fixed there
>
> ***
>
> 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
>
> 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.
--
Cheers, Lorenzo
prev parent reply other threads:[~2026-11-19 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 7:58 [PATCH v2 0/2] " Xu Xin (vivo)
2026-11-15 8:00 ` [PATCH v2 1/2] mm/ksm: extract helper functions for scan cycle cleanup Xu Xin (vivo)
2026-11-15 8:00 ` [PATCH v2 2/2] mm/ksm: add initialization helpers for scan_get_next_rmap_item() Xu Xin (vivo)
2026-11-15 15:28 ` kernel test robot
2026-11-19 7:00 ` [syzbot ci] Re: mm/ksm: clean up scan_get_next_rmap_item() initialization syzbot ci
2026-11-19 11:34 ` Lorenzo Stoakes (ARM) [this message]
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=av7e0B-1GCyk6sDs@gremlin \
--to=ljs@kernel.org \
--cc=chengming.zhou@linux.dev \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+ci7e1f981ab411668d@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xu.xin@linux.dev \
/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
all inboxes | Powered by JetHome®