[syzbot] [jfs?] BUG: unable to handle kernel paging request in diUpdatePMap

syzbot

unread,

Nov 7, 2025, 2:29:28 AM (yesterday) Nov 7

to jfs-dis...@lists.sourceforge.net, linux-...@vger.kernel.org, sha...@kernel.org, syzkall...@googlegroups.com

Hello,

syzbot found the following issue on:

HEAD commit: dcb6fa37fd7b Linux 6.18-rc3
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1451a532580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8b659f0cab27b22
dashboard link: https://syzkaller.appspot.com/bug?extid=7fc112f7a4a0546731c5
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17fc5812580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=110f3012580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ae6bec0d0398/disk-dcb6fa37.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dcc732da66c3/vmlinux-dcb6fa37.xz
kernel image: https://storage.googleapis.com/syzbot-assets/301d1bbdecc2/Image-dcb6fa37.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/94e5a8b9504e/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1051a532580000)

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7fc112...@syzkaller.appspotmail.com

Unable to handle kernel paging request at virtual address fbd5200000000021
KASAN: maybe wild-memory-access in range [0xdead000000000108-0xdead00000000010f]
Mem abort info:
ESR = 0x0000000096000004
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x04: level 0 translation fault
Data abort info:
ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
CM = 0, WnR = 0, TnD = 0, TagAccess = 0
GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[fbd5200000000021] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] SMP
Modules linked in:
CPU: 0 UID: 0 PID: 100 Comm: jfsCommit Not tainted syzkaller #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 834000c5 (Nzcv daIF +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : __list_add_valid_or_report+0x3c/0x148 lib/list_debug.c:29
lr : __list_add_valid include/linux/list.h:96 [inline]
lr : __list_add include/linux/list.h:158 [inline]
lr : list_add include/linux/list.h:177 [inline]
lr : diUpdatePMap+0x4e8/0xb90 fs/jfs/jfs_imap.c:2831
sp : ffff800099e67b50
x29: ffff800099e67b50 x28: dfff800000000000 x27: 00000000c0000000
x26: 0000000000000000 x25: dead000000000100 x24: 1bd5a00000000021
x23: dfff800000000000 x22: dead000000000108 x21: ffff0000e21152f8
x20: ffff80009b403120 x19: dead000000000100 x18: 0000000000000000
x17: ffff80010ca0e000 x16: ffff800080536ef4 x15: ffff7000133ccf58
x14: 1ffff000133ccf58 x13: 0000000000000004 x12: ffffffffffffffff
x11: ffff7000133ccf58 x10: 0000000000ff0100 x9 : 0000000000000000
x8 : 0000000000000000 x7 : ffff800081c11594 x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : ffff80008053700c
x2 : dead000000000100 x1 : ffff80009b403120 x0 : ffff0000e21152f8
Call trace:
__list_add_valid_or_report+0x3c/0x148 lib/list_debug.c:29 (P)
__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]
diUpdatePMap+0x4e8/0xb90 fs/jfs/jfs_imap.c:2831
txUpdateMap+0x708/0x8d0 fs/jfs/jfs_txnmgr.c:2357
txLazyCommit fs/jfs/jfs_txnmgr.c:2665 [inline]
jfs_lazycommit+0x394/0x94c fs/jfs/jfs_txnmgr.c:2734
kthread+0x5fc/0x75c kernel/kthread.c:463
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:844
Code: aa0103f4 d343fed8 f2fbfff7 aa0003f5 (38776b08)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: aa0103f4 mov x20, x1
4: d343fed8 lsr x24, x22, #3
8: f2fbfff7 movk x23, #0xdfff, lsl #48
c: aa0003f5 mov x21, x0
* 10: 38776b08 ldrb w8, [x24, x23] <-- trapping instruction

---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,

Nov 7, 2025, 5:02:08 AM (yesterday) Nov 7

to yun....@windriver.com, yun....@windriver.com, linux-...@vger.kernel.org, syzkall...@googlegroups.com

> #syz dup: https://syzkaller.appspot.com/bug?extid=4d0a0feb49c5138cac46

can't find the dup bug

>
>
> On 11/7/25 15:29, syzbot wrote:
>> CAUTION: This email comes from a non Wind River email account!
>> Do not click links or open attachments unless you recognize the sender and know the content is safe.

>> --
>> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bug...@googlegroups.com.
>> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-bugs/690d9fd4.a70a0220.22f260.0022.GAE%40google.com.
>

syzbot

unread,

Nov 7, 2025, 5:21:29 AM (yesterday) Nov 7

to linux-...@vger.kernel.org, syzkall...@googlegroups.com

For archival purposes, forwarding an incoming command email to
linux-...@vger.kernel.org, syzkall...@googlegroups.com.

***

Subject: Re: [syzbot] [jfs?] BUG: unable to handle kernel paging request in diUpdatePMap
Author: yun....@windriver.com

#syz test

diff --git a/fs/jfs/jfs_metapage.c b/fs/jfs/jfs_metapage.c
index 871cf4fb3636..0d6c40e7e551 100644
--- a/fs/jfs/jfs_metapage.c
+++ b/fs/jfs/jfs_metapage.c
@@ -270,6 +270,7 @@ static inline struct metapage *alloc_metapage(gfp_t
gfp_mask)
mp->clsn = 0;
mp->log = NULL;
init_waitqueue_head(&mp->wait);
+ INIT_LIST_HEAD(&mp->synclist);
}
return mp;
}
@@ -379,7 +380,7 @@ static void remove_from_logsync(struct metapage *mp)
mp->lsn = 0;
mp->clsn = 0;
log->count--;
- list_del(&mp->synclist);
+ list_del_init(&mp->synclist);
}
LOGSYNC_UNLOCK(log, flags);
}
diff --git a/fs/jfs/jfs_txnmgr.c b/fs/jfs/jfs_txnmgr.c
index 7840a03e5bcb..a5a5bc0a266d 100644
--- a/fs/jfs/jfs_txnmgr.c
+++ b/fs/jfs/jfs_txnmgr.c
@@ -275,6 +275,7 @@ int txInit(void)
for (k = 0; k < nTxBlock; k++) {
init_waitqueue_head(&TxBlock[k].gcwait);
init_waitqueue_head(&TxBlock[k].waitor);
+ INIT_LIST_HEAD(&TxBlock[k].synclist);
}

for (k = 1; k < nTxBlock - 1; k++) {
@@ -974,7 +975,7 @@ static void txUnlock(struct tblock * tblk)
if (tblk->lsn) {
LOGSYNC_LOCK(log, flags);
log->count--;
- list_del(&tblk->synclist);
+ list_del_init(&tblk->synclist);
LOGSYNC_UNLOCK(log, flags);
}
}

syzbot

unread,

Nov 7, 2025, 5:33:12 AM (yesterday) Nov 7

to linux-...@vger.kernel.org, syzkall...@googlegroups.com

For archival purposes, forwarding an incoming command email to
linux-...@vger.kernel.org, syzkall...@googlegroups.com.

***

Subject: Re: [syzbot] [jfs?] BUG: unable to handle kernel paging request in diUpdatePMap
Author: yun....@windriver.com

#syz dup: BUG: corrupted list in dbUpdatePMap

syzbot

unread,

Nov 7, 2025, 5:42:26 AM (yesterday) Nov 7

to linux-...@vger.kernel.org, syzkall...@googlegroups.com

For archival purposes, forwarding an incoming command email to
linux-...@vger.kernel.org, syzkall...@googlegroups.com.

***

Subject: Re: [syzbot] [jfs?] BUG: unable to handle kernel paging request in diUpdatePMap
Author: yun....@windriver.com

#syz dup: stack segment fault in diUpdatePMap

syzbot

unread,

Nov 7, 2025, 5:51:06 AM (yesterday) Nov 7

to linux-...@vger.kernel.org, syzkall...@googlegroups.com, yun....@windriver.com

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

failed to apply patch:
checking file fs/jfs/jfs_metapage.c
patch: **** malformed patch at line 6: diff --git a/fs/jfs/jfs_txnmgr.c b/fs/jfs/jfs_txnmgr.c

Tested on:

commit: dcb6fa37 Linux 6.18-rc3

git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci

kernel config: https://syzkaller.appspot.com/x/.config?x=b8b659f0cab27b22
dashboard link: https://syzkaller.appspot.com/bug?extid=7fc112f7a4a0546731c5
compiler:

userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=1729e17c580000

Zhou, Yun

unread,

Nov 7, 2025, 6:05:44 AM (yesterday) Nov 7

to syzkall...@googlegroups.com

On 11/7/25 15:29, syzbot wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>

syzbot

unread,

Nov 7, 2025, 6:15:42 AM (yesterday) Nov 7

to linux-...@vger.kernel.org, syzkall...@googlegroups.com

For archival purposes, forwarding an incoming command email to
linux-...@vger.kernel.org, syzkall...@googlegroups.com.

***

Subject: Re: [syzbot] [jfs?] BUG: unable to handle kernel paging request in diUpdatePMap
Author: yun....@windriver.com

Zhou, Yun

unread,

Nov 7, 2025, 6:31:02 AM (yesterday) Nov 7

to syzkall...@googlegroups.com

#syz test

0001-jfs-fix-corrupted-list-in-dbUpdatePMap.patch

syzbot

unread,

Nov 7, 2025, 6:32:04 AM (yesterday) Nov 7

to linux-...@vger.kernel.org, syzkall...@googlegroups.com, yun....@windriver.com

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

failed to apply patch:
checking file fs/jfs/jfs_metapage.c
patch: **** malformed patch at line 6: diff --git a/fs/jfs/jfs_txnmgr.c b/fs/jfs/jfs_txnmgr.c

Tested on:

commit: dcb6fa37 Linux 6.18-rc3

git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci

kernel config: https://syzkaller.appspot.com/x/.config?x=b8b659f0cab27b22
dashboard link: https://syzkaller.appspot.com/bug?extid=7fc112f7a4a0546731c5
compiler:

userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=15967012580000

syzbot

unread,

Nov 7, 2025, 7:31:08 AM (yesterday) Nov 7

to linux-...@vger.kernel.org, syzkall...@googlegroups.com, yun....@windriver.com

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KASAN: slab-use-after-free Read in release_metapage

==================================================================
BUG: KASAN: slab-use-after-free in drop_metapage fs/jfs/jfs_metapage.c:312 [inline]
BUG: KASAN: slab-use-after-free in release_metapage+0x678/0xa34 fs/jfs/jfs_metapage.c:893
Read of size 8 at addr ffff0000cf7dddb8 by task jfsCommit/99

CPU: 0 UID: 0 PID: 99 Comm: jfsCommit Not tainted syzkaller #0 PREEMPT

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025

Call trace:
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C)
__dump_stack+0x30/0x40 lib/dump_stack.c:94
dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120
print_address_description+0xa8/0x238 mm/kasan/report.c:378
print_report+0x68/0x84 mm/kasan/report.c:482
kasan_report+0xb0/0x110 mm/kasan/report.c:595
__asan_report_load8_noabort+0x20/0x2c mm/kasan/report_generic.c:381
drop_metapage fs/jfs/jfs_metapage.c:312 [inline]
release_metapage+0x678/0xa34 fs/jfs/jfs_metapage.c:893
put_metapage+0x1ec/0x288 fs/jfs/jfs_metapage.c:863
txUnlock+0x464/0xc98 fs/jfs/jfs_txnmgr.c:949
txLazyCommit fs/jfs/jfs_txnmgr.c:2684 [inline]
jfs_lazycommit+0x480/0x94c fs/jfs/jfs_txnmgr.c:2735

kthread+0x5fc/0x75c kernel/kthread.c:463
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:844

Allocated by task 7281:
kasan_save_stack mm/kasan/common.c:56 [inline]
kasan_save_track+0x40/0x78 mm/kasan/common.c:77
kasan_save_alloc_info+0x44/0x54 mm/kasan/generic.c:573
unpoison_slab_object mm/kasan/common.c:342 [inline]
__kasan_slab_alloc+0x70/0x88 mm/kasan/common.c:368
kasan_slab_alloc include/linux/kasan.h:252 [inline]
slab_post_alloc_hook mm/slub.c:4970 [inline]
slab_alloc_node mm/slub.c:5280 [inline]
kmem_cache_alloc_noprof+0x338/0x648 mm/slub.c:5287
mempool_alloc_slab+0x58/0x74 mm/mempool.c:587
mempool_alloc_noprof+0x150/0x3f4 mm/mempool.c:406
alloc_metapage fs/jfs/jfs_metapage.c:264 [inline]
__get_metapage+0x530/0xec8 fs/jfs/jfs_metapage.c:761
diNewExt+0x800/0x253c fs/jfs/jfs_imap.c:2275
diAllocExt fs/jfs/jfs_imap.c:1952 [inline]
diAllocAG+0x9bc/0x1a84 fs/jfs/jfs_imap.c:1669
diAlloc+0x17c/0x1630 fs/jfs/jfs_imap.c:1590
ialloc+0x80/0x78c fs/jfs/jfs_inode.c:56
jfs_mkdir+0x170/0x8b4 fs/jfs/namei.c:225
vfs_mkdir+0x284/0x424 fs/namei.c:4453
do_mkdirat+0x1f8/0x4c8 fs/namei.c:4486
__do_sys_mkdirat fs/namei.c:4503 [inline]
__se_sys_mkdirat fs/namei.c:4501 [inline]
__arm64_sys_mkdirat+0x8c/0xa4 fs/namei.c:4501
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49
el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
el0_svc+0x5c/0x254 arch/arm64/kernel/entry-common.c:746
el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:765
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596

Freed by task 7107:
kasan_save_stack mm/kasan/common.c:56 [inline]
kasan_save_track+0x40/0x78 mm/kasan/common.c:77
__kasan_save_free_info+0x58/0x70 mm/kasan/generic.c:587
kasan_save_free_info mm/kasan/kasan.h:406 [inline]
poison_slab_object mm/kasan/common.c:252 [inline]
__kasan_slab_free+0x74/0xa4 mm/kasan/common.c:284
kasan_slab_free include/linux/kasan.h:234 [inline]
slab_free_hook mm/slub.c:2539 [inline]
slab_free mm/slub.c:6630 [inline]
kmem_cache_free+0x18c/0x6dc mm/slub.c:6740
mempool_free_slab+0x28/0x38 mm/mempool.c:594
mempool_free+0xf8/0x5a0 mm/mempool.c:576
free_metapage fs/jfs/jfs_metapage.c:280 [inline]
metapage_release_folio+0x36c/0x484 fs/jfs/jfs_metapage.c:637
metapage_invalidate_folio+0x14c/0x1cc fs/jfs/jfs_metapage.c:672
folio_invalidate mm/truncate.c:140 [inline]
truncate_cleanup_folio+0x264/0x3a0 mm/truncate.c:160
truncate_inode_pages_range+0x1f4/0xe18 mm/truncate.c:379
truncate_inode_pages+0x2c/0x3c mm/truncate.c:460
jfs_put_super+0x124/0x188 fs/jfs/super.c:200
generic_shutdown_super+0x12c/0x2b8 fs/super.c:642
kill_block_super+0x44/0x90 fs/super.c:1722
deactivate_locked_super+0xc4/0x12c fs/super.c:473
deactivate_super+0xe0/0x100 fs/super.c:506
cleanup_mnt+0x31c/0x3ac fs/namespace.c:1327
__cleanup_mnt+0x20/0x30 fs/namespace.c:1334
task_work_run+0x1dc/0x260 kernel/task_work.c:227
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop+0xfc/0x178 kernel/entry/common.c:43
exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline]
arm64_exit_to_user_mode arch/arm64/kernel/entry-common.c:103 [inline]
el0_svc+0x170/0x254 arch/arm64/kernel/entry-common.c:747
el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:765
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596

The buggy address belongs to the object at ffff0000cf7ddd90
which belongs to the cache jfs_mp of size 184
The buggy address is located 40 bytes inside of
freed 184-byte region [ffff0000cf7ddd90, ffff0000cf7dde48)

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10f7dd
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
page_type: f5(slab)
raw: 05ffc00000000000 ffff0000c4c31000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000100010 00000000f5000000 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff0000cf7ddc80: fc fc fc fa fb fb fb fb fb fb fb fb fb fb fb fb
ffff0000cf7ddd00: fb fb fb fb fb fb fb fb fb fb fc fc fc fc fc fc
>ffff0000cf7ddd80: fc fc fa fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff0000cf7dde00: fb fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc
ffff0000cf7dde80: fc fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
Unable to handle kernel paging request at virtual address dfff800000000029
KASAN: null-ptr-deref in range [0x0000000000000148-0x000000000000014f]
Mem abort info:
ESR = 0x0000000096000005

EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0

FSC = 0x05: level 1 translation fault
Data abort info:
ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000

CM = 0, WnR = 0, TnD = 0, TagAccess = 0
GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0

[dfff800000000029] address between user and kernel address ranges
Internal error: Oops: 0000000096000005 [#1] SMP
Modules linked in:
CPU: 0 UID: 0 PID: 99 Comm: jfsCommit Tainted: G B syzkaller #0 PREEMPT
Tainted: [B]=BAD_PAGE

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025

pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : txEnd+0x180/0x4f0 fs/jfs/jfs_txnmgr.c:541
lr : txEnd+0x158/0x4f0 fs/jfs/jfs_txnmgr.c:530
sp : ffff8000993c7c60
x29: ffff8000993c7c60 x28: 1ffff00013680666 x27: ffff80008fb96000
x26: 1ffff00011f72cc4 x25: dfff800000000000 x24: ffff8000974a8000
x23: 0000000000000001 x22: 000000000000014c x21: ffff80009b403358
x20: 0000000000000003 x19: 0000000000000000 x18: 1fffe000337db690
x17: 3d3d3d3d3d3d3d3d x16: ffff8000802112a8 x15: 0000000000000001
x14: 1ffff0001368066c x13: 0000000000000000 x12: 0000000000000000
x11: ffff70001368066d x10: 0000000000ff0100 x9 : 0000000000000029
x8 : 0000000000000003 x7 : ffffffffffffffff x6 : ffff800080502e24
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800081c4c3ec
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
txEnd+0x180/0x4f0 fs/jfs/jfs_txnmgr.c:536 (P)
txLazyCommit fs/jfs/jfs_txnmgr.c:2686 [inline]
jfs_lazycommit+0x4b4/0x94c fs/jfs/jfs_txnmgr.c:2735

kthread+0x5fc/0x75c kernel/kthread.c:463
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:844

Code: 12003e88 790002b7 d343fec9 b902c308 (38f96928)

---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):

0: 12003e88 and w8, w20, #0xffff
4: 790002b7 strh w23, [x21]
8: d343fec9 lsr x9, x22, #3
c: b902c308 str w8, [x24, #704]
* 10: 38f96928 ldrsb w8, [x9, x25] <-- trapping instruction

Tested on:

commit: dcb6fa37 Linux 6.18-rc3
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci

console output: https://syzkaller.appspot.com/x/log.txt?x=17f7dbcd980000

kernel config: https://syzkaller.appspot.com/x/.config?x=b8b659f0cab27b22
dashboard link: https://syzkaller.appspot.com/bug?extid=7fc112f7a4a0546731c5

compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=15a7dbcd980000

Reply all

Reply to author

Forward