[moderation/CI] Re: mm: zone lock tracepoint instrumentation

[moderation/CI] Re: mm: zone lock tracepoint instrumentation

[syzbot ci]

syzbot ci has tested the following series

[v1] mm: zone lock tracepoint instrumentation
https://lore.kernel.org/all/cover.1770821420.git.d@ilvokhin.com
* [PATCH 1/4] mm: introduce zone lock wrappers
* [PATCH 2/4] mm: convert zone lock users to wrappers
* [PATCH 3/4] mm: convert compaction to zone lock wrappers
* [PATCH 4/4] mm: add tracepoints for zone lock

and found the following issue:
stack segment fault in dbUpdatePMap

Full report is available here:
https://ci.syzbot.org/series/43cf8aeb-42ac-4698-aa54-c296a912448f

***

stack segment fault in dbUpdatePMap

tree:      mm-new
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base:      af41d136f7932e545ba8b068fa5d352304b65078
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/9cea4e2f-a652-4347-a169-f8ad5ebd2284/config
syz repro: https://ci.syzbot.org/findings/edbdba1b-7fc9-4625-b875-9a2af033cb21/syz_repro

Oops: stack segment: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 117 Comm: jfsCommit 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:__list_add_valid_or_report+0x3e/0x130 lib/list_debug.c:29
Code: 00 00 00 48 89 d3 48 85 d2 0f 84 93 00 00 00 49 89 f6 49 89 ff 49 bd 00 00 00 00 00 fc ff df 4c 8d 63 08 4c 89 e5 48 c1 ed 03 <42> 80 7c 2d 00 00 74 08 4c 89 e7 e8 b2 f6 81 fd 4d 39 34 24 75 71
RSP: 0018:ffffc90003137a40 EFLAGS: 00010806
RAX: 0000000000000000 RBX: dead000000000100 RCX: 0000000000000000
RDX: dead000000000100 RSI: ffffc90002a79120 RDI: ffff88811d809ca8
RBP: 1bd5a00000000021 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000626f3c R12: dead000000000108
R13: dffffc0000000000 R14: ffffc90002a79120 R15: ffff88811d809ca8
FS:  0000000000000000(0000) GS:ffff88818e0f1000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055555c51ca28 CR3: 000000011316a000 CR4: 00000000000006f0
Call Trace:
 <TASK>
 __list_add_valid include/linux/list.h:96 [inline]
 __list_add include/linux/list.h:158 [inline]
 list_add include/linux/list.h:177 [inline]
 dbUpdatePMap+0x7ec/0xed0 fs/jfs/jfs_dmap.c:577
 txAllocPMap+0x57d/0x6b0 fs/jfs/jfs_txnmgr.c:2426
 txUpdateMap+0x81e/0x9c0 fs/jfs/jfs_txnmgr.c:2364
 txLazyCommit fs/jfs/jfs_txnmgr.c:2665 [inline]
 jfs_lazycommit+0x43d/0xaa0 fs/jfs/jfs_txnmgr.c:2734
 kthread+0x726/0x8b0 kernel/kthread.c:463
 ret_from_fork+0x51b/0xa40 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_add_valid_or_report+0x3e/0x130 lib/list_debug.c:29
Code: 00 00 00 48 89 d3 48 85 d2 0f 84 93 00 00 00 49 89 f6 49 89 ff 49 bd 00 00 00 00 00 fc ff df 4c 8d 63 08 4c 89 e5 48 c1 ed 03 <42> 80 7c 2d 00 00 74 08 4c 89 e7 e8 b2 f6 81 fd 4d 39 34 24 75 71
RSP: 0018:ffffc90003137a40 EFLAGS: 00010806
RAX: 0000000000000000 RBX: dead000000000100 RCX: 0000000000000000
RDX: dead000000000100 RSI: ffffc90002a79120 RDI: ffff88811d809ca8
RBP: 1bd5a00000000021 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000626f3c R12: dead000000000108
R13: dffffc0000000000 R14: ffffc90002a79120 R15: ffff88811d809ca8
FS:  0000000000000000(0000) GS:ffff88818e0f1000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055555c51ca28 CR3: 000000011316a000 CR4: 00000000000006f0
----------------
Code disassembly (best guess):
   0:	00 00                	add    %al,(%rax)
   2:	00 48 89             	add    %cl,-0x77(%rax)
   5:	d3 48 85             	rorl   %cl,-0x7b(%rax)
   8:	d2 0f                	rorb   %cl,(%rdi)
   a:	84 93 00 00 00 49    	test   %dl,0x49000000(%rbx)
  10:	89 f6                	mov    %esi,%esi
  12:	49 89 ff             	mov    %rdi,%r15
  15:	49 bd 00 00 00 00 00 	movabs $0xdffffc0000000000,%r13
  1c:	fc ff df
  1f:	4c 8d 63 08          	lea    0x8(%rbx),%r12
  23:	4c 89 e5             	mov    %r12,%rbp
  26:	48 c1 ed 03          	shr    $0x3,%rbp
* 2a:	42 80 7c 2d 00 00    	cmpb   $0x0,0x0(%rbp,%r13,1) <-- trapping instruction
  30:	74 08                	je     0x3a
  32:	4c 89 e7             	mov    %r12,%rdi
  35:	e8 b2 f6 81 fd       	call   0xfd81f6ec
  3a:	4d 39 34 24          	cmp    %r14,(%r12)
  3e:	75 71                	jne    0xb1


***

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 axelrasmussen@google.com d@ilvokhin.com david@kernel.org hannes@cmpxchg.org jackmanb@google.com kernel-team@meta.com liam.howlett@oracle.com linux-cxl@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org linux-trace-kernel@vger.kernel.org lorenzo.stoakes@oracle.com mathieu.desnoyers@efficios.com mhiramat@kernel.org mhocko@suse.com osalvador@suse.de rostedt@goodmis.org rppt@kernel.org shakeel.butt@linux.dev surenb@google.com vbabka@suse.cz weixugc@google.com yuanchu@google.com zhengqi.arch@bytedance.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

[moderation/CI] Re: mm: zone lock tracepoint instrumentation

[syzbot ci]

syzbot ci has tested the following series

[v3] mm: zone lock tracepoint instrumentation
https://lore.kernel.org/all/cover.1772129168.git.d@ilvokhin.com
* [PATCH v3 1/5] mm: introduce zone lock wrappers
* [PATCH v3 2/5] mm: convert zone lock users to wrappers
* [PATCH v3 3/5] mm: convert compaction to zone lock wrappers
* [PATCH v3 4/5] mm: rename zone->lock to zone->_lock
* [PATCH v3 5/5] mm: add tracepoints for zone lock

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/cfcd7061-63fb-4da3-abcb-ea888afce613

***

kernel build error

tree:      torvalds
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base:      3f4a08e64442340f4807de63e30aef22cc308830
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/f7743631-8ec3-49f9-ad7a-3e99f580cd40/config

kernel/power/snapshot.c:1254:27: error: no member named 'lock' in 'struct zone'
kernel/power/snapshot.c:1287:32: error: no member named 'lock' in 'struct zone'

***

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 axelrasmussen@google.com benjamin.cheatham@amd.com d@ilvokhin.com david@kernel.org hannes@cmpxchg.org jackmanb@google.com kernel-team@meta.com liam.howlett@oracle.com linux-cxl@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org linux-trace-kernel@vger.kernel.org lorenzo.stoakes@oracle.com mathieu.desnoyers@efficios.com mhiramat@kernel.org mhocko@suse.com osalvador@suse.de rostedt@goodmis.org rppt@kernel.org shakeel.butt@linux.dev surenb@google.com vbabka@suse.cz weixugc@google.com yuanchu@google.com zhengqi.arch@bytedance.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