[v5.15] BUG: corrupted list in dbUpdatePMap
0 views
Skip to first unread message
syzbot
Jan 2, 2026, 5:13:22 AM (6 days ago) Jan 2
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1658bfb4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=c0c71dfd0972587b1966
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c0c71d...@syzkaller.appspotmail.com
list_add corruption. next is NULL.
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:26!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 278 Comm: jfsCommit Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:__list_add_valid+0xb6/0xe0 lib/list_debug.c:25
Code: 4c 89 fe 4c 89 f2 48 89 d9 e8 a6 5e b8 05 0f 0b 48 c7 c7 c0 e8 59 8a e8 98 5e b8 05 0f 0b 48 c7 c7 60 e9 59 8a e8 8a 5e b8 05 <0f> 0b 48 c7 c7 c0 e9 59 8a 4c 89 f6 48 89 d9 e8 76 5e b8 05 0f 0b
RSP: 0018:ffffc90002d8fbd0 EFLAGS: 00010046
RAX: 0000000000000022 RBX: 0000000000000000 RCX: 357e2c0efae8e700
RDX: 0000000000000000 RSI: 0000000080000001 RDI: 0000000000000000
RBP: ffff888077d8221c R08: dffffc0000000000 R09: ffffed1017204f2c
R10: ffffed1017204f2c R11: 1ffff11017204f2b R12: 0000000000000000
R13: dffffc0000000000 R14: ffff88805cf76010 R15: 1ffff920004dc246
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8fcc7f4000 CR3: 000000002a9d2000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_add include/linux/list.h:67 [inline]
list_add include/linux/list.h:86 [inline]
dbUpdatePMap+0x6da/0xdb0 fs/jfs/jfs_dmap.c:577
txAllocPMap+0x57d/0x6b0 fs/jfs/jfs_txnmgr.c:2460
txUpdateMap+0x706/0x890 fs/jfs/jfs_txnmgr.c:2398
txLazyCommit fs/jfs/jfs_txnmgr.c:2699 [inline]
jfs_lazycommit+0x437/0xb20 fs/jfs/jfs_txnmgr.c:2767
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace c9725d50f2c33f50 ]---
RIP: 0010:__list_add_valid+0xb6/0xe0 lib/list_debug.c:25
Code: 4c 89 fe 4c 89 f2 48 89 d9 e8 a6 5e b8 05 0f 0b 48 c7 c7 c0 e8 59 8a e8 98 5e b8 05 0f 0b 48 c7 c7 60 e9 59 8a e8 8a 5e b8 05 <0f> 0b 48 c7 c7 c0 e9 59 8a 4c 89 f6 48 89 d9 e8 76 5e b8 05 0f 0b
RSP: 0018:ffffc90002d8fbd0 EFLAGS: 00010046
RAX: 0000000000000022 RBX: 0000000000000000 RCX: 357e2c0efae8e700
RDX: 0000000000000000 RSI: 0000000080000001 RDI: 0000000000000000
RBP: ffff888077d8221c R08: dffffc0000000000 R09: ffffed1017204f2c
R10: ffffed1017204f2c R11: 1ffff11017204f2b R12: 0000000000000000
R13: dffffc0000000000 R14: ffff88805cf76010 R15: 1ffff920004dc246
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8fcc7f4000 CR3: 000000002a9d2000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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 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 found the following issue on:
HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1658bfb4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=c0c71dfd0972587b1966
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c0c71d...@syzkaller.appspotmail.com
list_add corruption. next is NULL.
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:26!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 278 Comm: jfsCommit Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:__list_add_valid+0xb6/0xe0 lib/list_debug.c:25
Code: 4c 89 fe 4c 89 f2 48 89 d9 e8 a6 5e b8 05 0f 0b 48 c7 c7 c0 e8 59 8a e8 98 5e b8 05 0f 0b 48 c7 c7 60 e9 59 8a e8 8a 5e b8 05 <0f> 0b 48 c7 c7 c0 e9 59 8a 4c 89 f6 48 89 d9 e8 76 5e b8 05 0f 0b
RSP: 0018:ffffc90002d8fbd0 EFLAGS: 00010046
RAX: 0000000000000022 RBX: 0000000000000000 RCX: 357e2c0efae8e700
RDX: 0000000000000000 RSI: 0000000080000001 RDI: 0000000000000000
RBP: ffff888077d8221c R08: dffffc0000000000 R09: ffffed1017204f2c
R10: ffffed1017204f2c R11: 1ffff11017204f2b R12: 0000000000000000
R13: dffffc0000000000 R14: ffff88805cf76010 R15: 1ffff920004dc246
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8fcc7f4000 CR3: 000000002a9d2000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_add include/linux/list.h:67 [inline]
list_add include/linux/list.h:86 [inline]
dbUpdatePMap+0x6da/0xdb0 fs/jfs/jfs_dmap.c:577
txAllocPMap+0x57d/0x6b0 fs/jfs/jfs_txnmgr.c:2460
txUpdateMap+0x706/0x890 fs/jfs/jfs_txnmgr.c:2398
txLazyCommit fs/jfs/jfs_txnmgr.c:2699 [inline]
jfs_lazycommit+0x437/0xb20 fs/jfs/jfs_txnmgr.c:2767
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace c9725d50f2c33f50 ]---
RIP: 0010:__list_add_valid+0xb6/0xe0 lib/list_debug.c:25
Code: 4c 89 fe 4c 89 f2 48 89 d9 e8 a6 5e b8 05 0f 0b 48 c7 c7 c0 e8 59 8a e8 98 5e b8 05 0f 0b 48 c7 c7 60 e9 59 8a e8 8a 5e b8 05 <0f> 0b 48 c7 c7 c0 e9 59 8a 4c 89 f6 48 89 d9 e8 76 5e b8 05 0f 0b
RSP: 0018:ffffc90002d8fbd0 EFLAGS: 00010046
RAX: 0000000000000022 RBX: 0000000000000000 RCX: 357e2c0efae8e700
RDX: 0000000000000000 RSI: 0000000080000001 RDI: 0000000000000000
RBP: ffff888077d8221c R08: dffffc0000000000 R09: ffffed1017204f2c
R10: ffffed1017204f2c R11: 1ffff11017204f2b R12: 0000000000000000
R13: dffffc0000000000 R14: ffff88805cf76010 R15: 1ffff920004dc246
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8fcc7f4000 CR3: 000000002a9d2000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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 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
Jan 5, 2026, 6:23:25 AM (3 days ago) Jan 5
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=178b9efc580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127f4074580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f819abeaf140/mount_3.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=155a2e9a580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c0c71d...@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xfbd59c0000000021: 0000 [#1] PREEMPT SMP KASAN
KASAN: maybe wild-memory-access in range [0xdead000000000108-0xdead00000000010f]
CPU: 0 PID: 275 Comm: jfsCommit Not tainted syzkaller #0
Code: 00 00 00 48 89 d3 48 85 d2 0f 84 8c 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 e0 48 c1 e8 03 <42> 80 3c 28 00 74 08 4c 89 e7 e8 a8 24 dd fd 49 8b 14 24 4c 39 f2
RSP: 0018:ffffc9000254fbd0 EFLAGS: 00010806
RAX: 1bd5a00000000021 RBX: dead000000000100 RCX: ffff88801d910000
RDX: dead000000000100 RSI: ffffc900025d1230 RDI: ffff88801a1e5010
RBP: ffff88807b1eba1c R08: 0000000000000004 R09: 0000000000000003
R10: fffff520004a9f5c R11: 1ffff920004a9f5c R12: dead000000000108
R13: dffffc0000000000 R14: ffffc900025d1230 R15: ffff88801a1e5010
RIP: 0010:__list_add_valid+0x39/0xe0 lib/list_debug.c:27
Code: 00 00 00 48 89 d3 48 85 d2 0f 84 8c 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 e0 48 c1 e8 03 <42> 80 3c 28 00 74 08 4c 89 e7 e8 a8 24 dd fd 49 8b 14 24 4c 39 f2
RSP: 0018:ffffc9000254fbd0 EFLAGS: 00010806
RAX: 1bd5a00000000021 RBX: dead000000000100 RCX: ffff88801d910000
RDX: dead000000000100 RSI: ffffc900025d1230 RDI: ffff88801a1e5010
RBP: ffff88807b1eba1c R08: 0000000000000004 R09: 0000000000000003
R10: fffff520004a9f5c R11: 1ffff920004a9f5c R12: dead000000000108
R13: dffffc0000000000 R14: ffffc900025d1230 R15: ffff88801a1e5010
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 8c 00 00 00 49 89 test %cl,-0x76b70000(%rax,%rax,1)
11: f6 49 89 ff testb $0xff,-0x77(%rcx)
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 e0 mov %r12,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 4c 89 e7 mov %r12,%rdi
34: e8 a8 24 dd fd call 0xfddd24e1
39: 49 8b 14 24 mov (%r12),%rdx
3d: 4c 39 f2 cmp %r14,%rdx
---
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.
HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=c0c71dfd0972587b1966
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1027cf92580000
dashboard link: https://syzkaller.appspot.com/bug?extid=c0c71dfd0972587b1966
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127f4074580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=155a2e9a580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c0c71d...@syzkaller.appspotmail.com
KASAN: maybe wild-memory-access in range [0xdead000000000108-0xdead00000000010f]
CPU: 0 PID: 275 Comm: jfsCommit Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:__list_add_valid+0x39/0xe0 lib/list_debug.c:27
Code: 00 00 00 48 89 d3 48 85 d2 0f 84 8c 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 e0 48 c1 e8 03 <42> 80 3c 28 00 74 08 4c 89 e7 e8 a8 24 dd fd 49 8b 14 24 4c 39 f2
RSP: 0018:ffffc9000254fbd0 EFLAGS: 00010806
RAX: 1bd5a00000000021 RBX: dead000000000100 RCX: ffff88801d910000
RDX: dead000000000100 RSI: ffffc900025d1230 RDI: ffff88801a1e5010
RBP: ffff88807b1eba1c R08: 0000000000000004 R09: 0000000000000003
R10: fffff520004a9f5c R11: 1ffff920004a9f5c R12: dead000000000108
R13: dffffc0000000000 R14: ffffc900025d1230 R15: ffff88801a1e5010
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4d3a45e000 CR3: 000000001f735000 CR4: 00000000003506f0
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_add include/linux/list.h:67 [inline]
list_add include/linux/list.h:86 [inline]
dbUpdatePMap+0x6da/0xdb0 fs/jfs/jfs_dmap.c:577
txAllocPMap+0x57d/0x6b0 fs/jfs/jfs_txnmgr.c:2460
txUpdateMap+0x706/0x890 fs/jfs/jfs_txnmgr.c:2398
txLazyCommit fs/jfs/jfs_txnmgr.c:2699 [inline]
jfs_lazycommit+0x437/0xb20 fs/jfs/jfs_txnmgr.c:2767
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace 7408fc197fce9b7e ]---
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_add include/linux/list.h:67 [inline]
list_add include/linux/list.h:86 [inline]
dbUpdatePMap+0x6da/0xdb0 fs/jfs/jfs_dmap.c:577
txAllocPMap+0x57d/0x6b0 fs/jfs/jfs_txnmgr.c:2460
txUpdateMap+0x706/0x890 fs/jfs/jfs_txnmgr.c:2398
txLazyCommit fs/jfs/jfs_txnmgr.c:2699 [inline]
jfs_lazycommit+0x437/0xb20 fs/jfs/jfs_txnmgr.c:2767
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
RIP: 0010:__list_add_valid+0x39/0xe0 lib/list_debug.c:27
Code: 00 00 00 48 89 d3 48 85 d2 0f 84 8c 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 e0 48 c1 e8 03 <42> 80 3c 28 00 74 08 4c 89 e7 e8 a8 24 dd fd 49 8b 14 24 4c 39 f2
RSP: 0018:ffffc9000254fbd0 EFLAGS: 00010806
RAX: 1bd5a00000000021 RBX: dead000000000100 RCX: ffff88801d910000
RDX: dead000000000100 RSI: ffffc900025d1230 RDI: ffff88801a1e5010
RBP: ffff88807b1eba1c R08: 0000000000000004 R09: 0000000000000003
R10: fffff520004a9f5c R11: 1ffff920004a9f5c R12: dead000000000108
R13: dffffc0000000000 R14: ffffc900025d1230 R15: ffff88801a1e5010
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4d3a45e000 CR3: 000000001f735000 CR4: 00000000003506f0
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
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 8c 00 00 00 49 89 test %cl,-0x76b70000(%rax,%rax,1)
11: f6 49 89 ff testb $0xff,-0x77(%rcx)
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 e0 mov %r12,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 4c 89 e7 mov %r12,%rdi
34: e8 a8 24 dd fd call 0xfddd24e1
39: 49 8b 14 24 mov (%r12),%rdx
3d: 4c 39 f2 cmp %r14,%rdx
---
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.
Reply all
Reply to author
Forward
0 new messages