* [syzbot] [jfs?] stack segment fault in dbUpdatePMap
@ 2025-11-01 17:24 syzbot
2025-11-01 19:01 ` syzbot
2025-11-10 11:30 ` Forwarded: test syzbot
0 siblings, 2 replies; 24+ messages in thread
From: syzbot @ 2025-11-01 17:24 UTC (permalink / raw)
To: jfs-discussion, linux-kernel, shaggy, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: ba36dd5ee6fd Merge tag 'bpf-fixes' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1145ae14580000
kernel config: https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
dashboard link: https://syzkaller.appspot.com/bug?extid=f5a5b157b7336d1fda1d
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/b151a6a8b947/disk-ba36dd5e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ddc072fd4513/vmlinux-ba36dd5e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7cdcc5b6e230/bzImage-ba36dd5e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f5a5b157b7336d1fda1d@syzkaller.appspotmail.com
Oops: stack segment: 0000 [#1] SMP KASAN PTI
CPU: 1 UID: 0 PID: 122 Comm: jfsCommit Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
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 32 c4 9d fd 4d 39 34 24 75 71
RSP: 0018:ffffc900031f7a20 EFLAGS: 00010a06
RAX: 0000000000000000 RBX: dead000000000100 RCX: ffff88801dbc9e00
RDX: dead000000000100 RSI: ffffc9000323a140 RDI: ffff88802f4c9898
RBP: 1bd5a00000000021 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff1dac5cf R12: dead000000000108
R13: dffffc0000000000 R14: ffffc9000323a140 R15: ffff88802f4c9898
FS: 0000000000000000(0000) GS:ffff888126ef9000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555586d63608 CR3: 0000000038d96000 CR4: 00000000003526f0
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+0x7e4/0xeb0 fs/jfs/jfs_dmap.c:577
txAllocPMap+0x57d/0x6b0 fs/jfs/jfs_txnmgr.c:2426
txUpdateMap+0x2a2/0x9c0 fs/jfs/jfs_txnmgr.c:2309
txLazyCommit fs/jfs/jfs_txnmgr.c:2665 [inline]
jfs_lazycommit+0x3f1/0xa10 fs/jfs/jfs_txnmgr.c:2734
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</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 32 c4 9d fd 4d 39 34 24 75 71
RSP: 0018:ffffc900031f7a20 EFLAGS: 00010a06
RAX: 0000000000000000 RBX: dead000000000100 RCX: ffff88801dbc9e00
RDX: dead000000000100 RSI: ffffc9000323a140 RDI: ffff88802f4c9898
RBP: 1bd5a00000000021 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff1dac5cf R12: dead000000000108
R13: dffffc0000000000 R14: ffffc9000323a140 R15: ffff88802f4c9898
FS: 0000000000000000(0000) GS:ffff888126ef9000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555586d63608 CR3: 0000000038d96000 CR4: 00000000003526f0
----------------
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 32 c4 9d fd call 0xfd9dc46c
3a: 4d 39 34 24 cmp %r14,(%r12)
3e: 75 71 jne 0xb1
---
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 syzkaller@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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [syzbot] [jfs?] stack segment fault in dbUpdatePMap
2025-11-01 17:24 [syzbot] [jfs?] stack segment fault in dbUpdatePMap syzbot
@ 2025-11-01 19:01 ` syzbot
2025-11-10 11:30 ` Forwarded: test syzbot
1 sibling, 0 replies; 24+ messages in thread
From: syzbot @ 2025-11-01 19:01 UTC (permalink / raw)
To: jfs-discussion, linux-kernel, shaggy, syzkaller-bugs
syzbot has found a reproducer for the following issue on:
HEAD commit: ba36dd5ee6fd Merge tag 'bpf-fixes' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16032342580000
kernel config: https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
dashboard link: https://syzkaller.appspot.com/bug?extid=f5a5b157b7336d1fda1d
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=1760b932580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ca3258580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b151a6a8b947/disk-ba36dd5e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ddc072fd4513/vmlinux-ba36dd5e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7cdcc5b6e230/bzImage-ba36dd5e.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/d873406bb3bb/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=113b4292580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f5a5b157b7336d1fda1d@syzkaller.appspotmail.com
Oops: stack segment: 0000 [#1] SMP KASAN PTI
CPU: 1 UID: 0 PID: 122 Comm: jfsCommit Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
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 32 c4 9d fd 4d 39 34 24 75 71
RSP: 0018:ffffc900039e7a20 EFLAGS: 00010a06
RAX: 0000000000000000 RBX: dead000000000100 RCX: ffff88801ff1bc00
RDX: dead000000000100 RSI: ffffc90003229330 RDI: ffff88814729dc40
RBP: 1bd5a00000000021 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff1dac5cf R12: dead000000000108
R13: dffffc0000000000 R14: ffffc90003229330 R15: ffff88814729dc40
FS: 0000000000000000(0000) GS:ffff888126ef9000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fffcb89299c CR3: 0000000035922000 CR4: 00000000003526f0
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+0x7e4/0xeb0 fs/jfs/jfs_dmap.c:577
txAllocPMap+0x57d/0x6b0 fs/jfs/jfs_txnmgr.c:2426
txUpdateMap+0x2a2/0x9c0 fs/jfs/jfs_txnmgr.c:2309
txLazyCommit fs/jfs/jfs_txnmgr.c:2665 [inline]
jfs_lazycommit+0x3f1/0xa10 fs/jfs/jfs_txnmgr.c:2734
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</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 32 c4 9d fd 4d 39 34 24 75 71
RSP: 0018:ffffc900039e7a20 EFLAGS: 00010a06
RAX: 0000000000000000 RBX: dead000000000100 RCX: ffff88801ff1bc00
RDX: dead000000000100 RSI: ffffc90003229330 RDI: ffff88814729dc40
RBP: 1bd5a00000000021 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff1dac5cf R12: dead000000000108
R13: dffffc0000000000 R14: ffffc90003229330 R15: ffff88814729dc40
FS: 0000000000000000(0000) GS:ffff888126ef9000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fffcb89299c CR3: 0000000035922000 CR4: 00000000003526f0
----------------
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 32 c4 9d fd call 0xfd9dc46c
3a: 4d 39 34 24 cmp %r14,(%r12)
3e: 75 71 jne 0xb1
---
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.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2025-11-01 17:24 [syzbot] [jfs?] stack segment fault in dbUpdatePMap syzbot
2025-11-01 19:01 ` syzbot
@ 2025-11-10 11:30 ` syzbot
1 sibling, 0 replies; 24+ messages in thread
From: syzbot @ 2025-11-10 11:30 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2024-08-16 5:17 [syzbot] [xfs?] INFO: task hung in xfs_buf_item_unpin (2) syzbot
@ 2026-07-13 14:52 ` syzbot
0 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2026-07-13 14:52 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2024-08-28 0:09 [syzbot] [nbd?] INFO: task hung in nbd_queue_rq syzbot
@ 2026-07-07 11:25 ` syzbot
0 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2026-07-07 11:25 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2026-07-06 21:44 [syzbot] [netfs?] WARNING in netfs_writepages (3) syzbot
@ 2026-07-07 5:34 ` syzbot
0 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2026-07-07 5:34 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2025-11-13 8:08 [syzbot] [ext4?] possible deadlock in ext4_xattr_set_handle (7) syzbot
@ 2026-06-09 8:41 ` syzbot
0 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2026-06-09 8:41 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2026-06-04 21:33 [syzbot] [overlayfs?] [ext4?] possible deadlock in lock_two_nondirectories (2) syzbot
@ 2026-06-08 15:46 ` syzbot
0 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2026-06-08 15:46 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2026-05-31 1:20 [syzbot] [block?] general protection fault in ublk_queue_rq syzbot
@ 2026-06-01 18:58 ` syzbot
0 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2026-06-01 18:58 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2026-05-19 18:53 [syzbot] [net?] possible deadlock in __sk_receive_skb syzbot
` (2 preceding siblings ...)
2026-05-20 10:27 ` syzbot
@ 2026-05-20 14:33 ` syzbot
3 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2026-05-20 14:33 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2026-05-19 18:53 [syzbot] [net?] possible deadlock in __sk_receive_skb syzbot
2026-05-20 2:05 ` Forwarded: test syzbot
2026-05-20 9:15 ` syzbot
@ 2026-05-20 10:27 ` syzbot
2026-05-20 14:33 ` syzbot
3 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2026-05-20 10:27 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2026-05-19 11:56 [syzbot] [net?] WARNING in netif_rx_mode_run syzbot
2026-05-19 12:49 ` Forwarded: test syzbot
@ 2026-05-20 9:34 ` syzbot
1 sibling, 0 replies; 24+ messages in thread
From: syzbot @ 2026-05-20 9:34 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2026-05-19 18:53 [syzbot] [net?] possible deadlock in __sk_receive_skb syzbot
2026-05-20 2:05 ` Forwarded: test syzbot
@ 2026-05-20 9:15 ` syzbot
2026-05-20 10:27 ` syzbot
2026-05-20 14:33 ` syzbot
3 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2026-05-20 9:15 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2026-05-19 18:53 [syzbot] [net?] possible deadlock in __sk_receive_skb syzbot
@ 2026-05-20 2:05 ` syzbot
2026-05-20 9:15 ` syzbot
` (2 subsequent siblings)
3 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2026-05-20 2:05 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2026-05-19 11:56 [syzbot] [net?] WARNING in netif_rx_mode_run syzbot
@ 2026-05-19 12:49 ` syzbot
2026-05-20 9:34 ` syzbot
1 sibling, 0 replies; 24+ messages in thread
From: syzbot @ 2026-05-19 12:49 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2026-05-18 1:17 [syzbot] [media?] KASAN: slab-use-after-free Read in dvb_frontend_open syzbot
2026-05-18 11:19 ` Forwarded: test syzbot
@ 2026-05-19 0:36 ` syzbot
1 sibling, 0 replies; 24+ messages in thread
From: syzbot @ 2026-05-19 0:36 UTC (permalink / raw)
To: linux-kernel
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2026-05-18 1:17 [syzbot] [media?] KASAN: slab-use-after-free Read in dvb_frontend_open syzbot
@ 2026-05-18 11:19 ` syzbot
2026-05-19 0:36 ` syzbot
1 sibling, 0 replies; 24+ messages in thread
From: syzbot @ 2026-05-18 11:19 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2023-01-16 16:40 [syzbot] possible deadlock in br_multicast_rcv (3) syzbot
@ 2026-04-23 16:10 ` syzbot
0 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2026-04-23 16:10 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: idosch@nvidia.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2025-04-30 13:26 [syzbot] [jfs?] UBSAN: shift-out-of-bounds in jfs_statfs (3) syzbot
@ 2025-11-20 15:15 ` syzbot
0 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2025-11-20 15:15 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2025-04-30 21:08 [syzbot] [jfs?] UBSAN: shift-out-of-bounds in dbSplit (3) syzbot
@ 2025-11-19 2:55 ` syzbot
0 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2025-11-19 2:55 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2024-10-03 19:10 [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in dtInsertEntry syzbot
@ 2025-11-18 14:11 ` syzbot
0 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2025-11-18 14:11 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
diff --git a/fs/jfs/jfs_txnmgr.h b/fs/jfs/jfs_txnmgr.h
index ba71eb5ced56..391c0d28e1bc 100644
--- a/fs/jfs/jfs_txnmgr.h
+++ b/fs/jfs/jfs_txnmgr.h
@@ -165,7 +165,7 @@ struct linelock {
u8 l2linesize; /* 1: log2 of linesize */
/* (8) */
- struct lv lv[20]; /* 40: */
+ struct lv lv[]; /* 40: */
}; /* (48) */
#define dt_lock linelock
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2025-11-07 7:29 [syzbot] [jfs?] general protection fault in txCommit (2) syzbot
2025-11-14 13:48 ` Forwarded: test syzbot
@ 2025-11-14 14:36 ` syzbot
1 sibling, 0 replies; 24+ messages in thread
From: syzbot @ 2025-11-14 14:36 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2025-11-07 7:29 [syzbot] [jfs?] general protection fault in txCommit (2) syzbot
@ 2025-11-14 13:48 ` syzbot
2025-11-14 14:36 ` syzbot
1 sibling, 0 replies; 24+ messages in thread
From: syzbot @ 2025-11-14 13:48 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: yun.zhou@windriver.com
#syz test
^ permalink raw reply [flat|nested] 24+ messages in thread
* Forwarded: test
2025-09-30 20:29 [syzbot] [rdma?] KMSAN: uninit-value in ib_nl_handle_ip_res_resp syzbot
@ 2025-11-06 19:28 ` syzbot
0 siblings, 0 replies; 24+ messages in thread
From: syzbot @ 2025-11-06 19:28 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: test
Author: kriish.sharma2006@gmail.com
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
566771afc7a8
^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2026-07-13 14:52 UTC | newest]
Thread overview: 24+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-11-01 17:24 [syzbot] [jfs?] stack segment fault in dbUpdatePMap syzbot
2025-11-01 19:01 ` syzbot
2025-11-10 11:30 ` Forwarded: test syzbot
-- strict thread matches above, loose matches on Subject: below --
2026-07-06 21:44 [syzbot] [netfs?] WARNING in netfs_writepages (3) syzbot
2026-07-07 5:34 ` Forwarded: test syzbot
2026-06-04 21:33 [syzbot] [overlayfs?] [ext4?] possible deadlock in lock_two_nondirectories (2) syzbot
2026-06-08 15:46 ` Forwarded: test syzbot
2026-05-31 1:20 [syzbot] [block?] general protection fault in ublk_queue_rq syzbot
2026-06-01 18:58 ` Forwarded: test syzbot
2026-05-19 18:53 [syzbot] [net?] possible deadlock in __sk_receive_skb syzbot
2026-05-20 2:05 ` Forwarded: test syzbot
2026-05-20 9:15 ` syzbot
2026-05-20 10:27 ` syzbot
2026-05-20 14:33 ` syzbot
2026-05-19 11:56 [syzbot] [net?] WARNING in netif_rx_mode_run syzbot
2026-05-19 12:49 ` Forwarded: test syzbot
2026-05-20 9:34 ` syzbot
2026-05-18 1:17 [syzbot] [media?] KASAN: slab-use-after-free Read in dvb_frontend_open syzbot
2026-05-18 11:19 ` Forwarded: test syzbot
2026-05-19 0:36 ` syzbot
2025-11-13 8:08 [syzbot] [ext4?] possible deadlock in ext4_xattr_set_handle (7) syzbot
2026-06-09 8:41 ` Forwarded: test syzbot
2025-11-07 7:29 [syzbot] [jfs?] general protection fault in txCommit (2) syzbot
2025-11-14 13:48 ` Forwarded: test syzbot
2025-11-14 14:36 ` syzbot
2025-09-30 20:29 [syzbot] [rdma?] KMSAN: uninit-value in ib_nl_handle_ip_res_resp syzbot
2025-11-06 19:28 ` Forwarded: test syzbot
2025-04-30 21:08 [syzbot] [jfs?] UBSAN: shift-out-of-bounds in dbSplit (3) syzbot
2025-11-19 2:55 ` Forwarded: test syzbot
2025-04-30 13:26 [syzbot] [jfs?] UBSAN: shift-out-of-bounds in jfs_statfs (3) syzbot
2025-11-20 15:15 ` Forwarded: test syzbot
2024-10-03 19:10 [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in dtInsertEntry syzbot
2025-11-18 14:11 ` Forwarded: test syzbot
2024-08-28 0:09 [syzbot] [nbd?] INFO: task hung in nbd_queue_rq syzbot
2026-07-07 11:25 ` Forwarded: test syzbot
2024-08-16 5:17 [syzbot] [xfs?] INFO: task hung in xfs_buf_item_unpin (2) syzbot
2026-07-13 14:52 ` Forwarded: test syzbot
2023-01-16 16:40 [syzbot] possible deadlock in br_multicast_rcv (3) syzbot
2026-04-23 16:10 ` Forwarded: test syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome