* [syzbot] possible deadlock in page_cache_ra_unbounded
@ 2022-12-21 8:15 syzbot
2023-06-26 23:27 ` [syzbot] [reiserfs?] " syzbot
` (2 more replies)
0 siblings, 3 replies; 134+ messages in thread
From: syzbot @ 2022-12-21 8:15 UTC (permalink / raw)
To: akpm, linux-fsdevel, linux-kernel, linux-mm, syzkaller-bugs, willy
Hello,
syzbot found the following issue on:
HEAD commit: 6feb57c2fd7c Merge tag 'kbuild-v6.2' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13abf993880000
kernel config: https://syzkaller.appspot.com/x/.config?x=d3fb546de56fbf8d
dashboard link: https://syzkaller.appspot.com/bug?extid=47c7e14e1bd09234d0ad
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/81556e491789/disk-6feb57c2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/065c943ec9de/vmlinux-6feb57c2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/66e98c522c1f/bzImage-6feb57c2.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+47c7e14e1bd09234d0ad@syzkaller.appspotmail.com
REISERFS (device loop4): Created .reiserfs_priv - reserved for xattr storage.
======================================================
WARNING: possible circular locking dependency detected
6.1.0-syzkaller-13822-g6feb57c2fd7c #0 Not tainted
------------------------------------------------------
syz-executor.4/3542 is trying to acquire lock:
ffff88803bf4f520 (mapping.invalidate_lock#11){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
ffff88803bf4f520 (mapping.invalidate_lock#11){.+.+}-{3:3}, at: page_cache_ra_unbounded+0xe9/0x820 mm/readahead.c:226
but task is already holding lock:
ffff88802540e090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x77/0xd0 fs/reiserfs/lock.c:27
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&sbi->lock){+.+.}-{3:3}:
lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668
__mutex_lock_common+0x1bd/0x26e0 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
reiserfs_write_lock+0x77/0xd0 fs/reiserfs/lock.c:27
reiserfs_get_block+0x24e/0x5180 fs/reiserfs/inode.c:680
do_mpage_readpage+0x970/0x1c50 fs/mpage.c:208
mpage_readahead+0x210/0x380 fs/mpage.c:361
read_pages+0x169/0x9c0 mm/readahead.c:161
page_cache_ra_unbounded+0x703/0x820 mm/readahead.c:270
page_cache_sync_readahead include/linux/pagemap.h:1210 [inline]
filemap_get_pages+0x465/0x10d0 mm/filemap.c:2600
filemap_read+0x3cf/0xea0 mm/filemap.c:2694
call_read_iter include/linux/fs.h:2180 [inline]
generic_file_splice_read+0x1ff/0x5d0 fs/splice.c:309
do_splice_to fs/splice.c:793 [inline]
splice_direct_to_actor+0x41b/0xc00 fs/splice.c:865
do_splice_direct+0x279/0x3d0 fs/splice.c:974
do_sendfile+0x5fb/0xf80 fs/read_write.c:1255
__do_sys_sendfile64 fs/read_write.c:1323 [inline]
__se_sys_sendfile64+0x14f/0x1b0 fs/read_write.c:1309
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #0 (mapping.invalidate_lock#11){.+.+}-{3:3}:
check_prev_add kernel/locking/lockdep.c:3097 [inline]
check_prevs_add kernel/locking/lockdep.c:3216 [inline]
validate_chain+0x1898/0x6ae0 kernel/locking/lockdep.c:3831
__lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055
lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668
down_read+0x39/0x50 kernel/locking/rwsem.c:1509
filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
page_cache_ra_unbounded+0xe9/0x820 mm/readahead.c:226
do_sync_mmap_readahead+0x4b2/0x9a0
filemap_fault+0x38d/0x1060 mm/filemap.c:3154
__do_fault+0x136/0x4f0 mm/memory.c:4163
do_shared_fault mm/memory.c:4569 [inline]
do_fault mm/memory.c:4647 [inline]
handle_pte_fault mm/memory.c:4931 [inline]
__handle_mm_fault mm/memory.c:5073 [inline]
handle_mm_fault+0x18bc/0x26b0 mm/memory.c:5219
do_user_addr_fault+0x69b/0xcb0 arch/x86/mm/fault.c:1428
handle_page_fault arch/x86/mm/fault.c:1519 [inline]
exc_page_fault+0x7a/0x110 arch/x86/mm/fault.c:1575
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570
__put_user_4+0x12/0x20 arch/x86/lib/putuser.S:93
reiserfs_ioctl+0x14b/0x340 fs/reiserfs/ioctl.c:96
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&sbi->lock);
lock(mapping.invalidate_lock#11);
lock(&sbi->lock);
lock(mapping.invalidate_lock#11);
*** DEADLOCK ***
1 lock held by syz-executor.4/3542:
#0: ffff88802540e090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x77/0xd0 fs/reiserfs/lock.c:27
stack backtrace:
CPU: 1 PID: 3542 Comm: syz-executor.4 Not tainted 6.1.0-syzkaller-13822-g6feb57c2fd7c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1b1/0x290 lib/dump_stack.c:106
check_noncircular+0x2cc/0x390 kernel/locking/lockdep.c:2177
check_prev_add kernel/locking/lockdep.c:3097 [inline]
check_prevs_add kernel/locking/lockdep.c:3216 [inline]
validate_chain+0x1898/0x6ae0 kernel/locking/lockdep.c:3831
__lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055
lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668
down_read+0x39/0x50 kernel/locking/rwsem.c:1509
filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
page_cache_ra_unbounded+0xe9/0x820 mm/readahead.c:226
do_sync_mmap_readahead+0x4b2/0x9a0
filemap_fault+0x38d/0x1060 mm/filemap.c:3154
__do_fault+0x136/0x4f0 mm/memory.c:4163
do_shared_fault mm/memory.c:4569 [inline]
do_fault mm/memory.c:4647 [inline]
handle_pte_fault mm/memory.c:4931 [inline]
__handle_mm_fault mm/memory.c:5073 [inline]
handle_mm_fault+0x18bc/0x26b0 mm/memory.c:5219
do_user_addr_fault+0x69b/0xcb0 arch/x86/mm/fault.c:1428
handle_page_fault arch/x86/mm/fault.c:1519 [inline]
exc_page_fault+0x7a/0x110 arch/x86/mm/fault.c:1575
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0010:__put_user_4+0x12/0x20 arch/x86/lib/putuser.S:95
Code: 01 31 c9 0f 01 ca c3 90 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 40 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 54 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 0f 01 cb 89 01 31 c9 0f
RSP: 0018:ffffc90014c97eb0 EFLAGS: 00050297
RAX: 0000000000000000 RBX: 00007fffffffeffd RCX: 0000000020000000
RDX: 0000000000000001 RSI: ffffffff8aedcc60 RDI: ffffffff8b4bc060
RBP: 1ffff110077e9e4b R08: dffffc0000000000 R09: fffffbfff1d2ccfe
R10: fffffbfff1d2ccfe R11: 1ffffffff1d2ccfd R12: 0000000020000000
R13: ffff88803bf4f698 R14: ffff88803bf4f258 R15: ffff8880205c9400
reiserfs_ioctl+0x14b/0x340 fs/reiserfs/ioctl.c:96
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f0a0548c0d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f0a061d5168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f0a055abf80 RCX: 00007f0a0548c0d9
RDX: 0000000020000000 RSI: 0000000080087601 RDI: 0000000000000004
RBP: 00007f0a054e7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc8aa2e79f R14: 00007f0a061d5300 R15: 0000000000022000
</TASK>
----------------
Code disassembly (best guess):
0: 01 31 add %esi,(%rcx)
2: c9 leaveq
3: 0f 01 ca clac
6: c3 retq
7: 90 nop
8: 0f 01 cb stac
b: 66 89 01 mov %ax,(%rcx)
e: 31 c9 xor %ecx,%ecx
10: 0f 01 ca clac
13: c3 retq
14: 0f 1f 40 00 nopl 0x0(%rax)
18: 48 bb fd ef ff ff ff movabs $0x7fffffffeffd,%rbx
1f: 7f 00 00
22: 48 39 d9 cmp %rbx,%rcx
25: 73 54 jae 0x7b
27: 0f 01 cb stac
* 2a: 89 01 mov %eax,(%rcx) <-- trapping instruction
2c: 31 c9 xor %ecx,%ecx
2e: 0f 01 ca clac
31: c3 retq
32: 66 0f 1f 44 00 00 nopw 0x0(%rax,%rax,1)
38: 0f 01 cb stac
3b: 89 01 mov %eax,(%rcx)
3d: 31 c9 xor %ecx,%ecx
3f: 0f .byte 0xf
---
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.
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot] [reiserfs?] possible deadlock in page_cache_ra_unbounded
2022-12-21 8:15 [syzbot] possible deadlock in page_cache_ra_unbounded syzbot
@ 2023-06-26 23:27 ` syzbot
2025-01-08 16:11 ` [syzbot] syzbot
2025-02-20 16:20 ` [syzbot] [mm] [fs] possible deadlock in page_cache_ra_unbounded syzbot
2 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2023-06-26 23:27 UTC (permalink / raw)
To: akpm, linux-fsdevel, linux-kernel, linux-mm, reiserfs-devel,
syzkaller-bugs, willy
syzbot has found a reproducer for the following issue on:
HEAD commit: c0a572d9d32f Merge tag 'v6.5/vfs.mount' of git://git.kerne..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=11d54c0b280000
kernel config: https://syzkaller.appspot.com/x/.config?x=f4df35260418daa6
dashboard link: https://syzkaller.appspot.com/bug?extid=47c7e14e1bd09234d0ad
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11c01f00a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=145add7b280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1855f91c7ed0/disk-c0a572d9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fbbea26cfe51/vmlinux-c0a572d9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5c9ca7f2d7aa/bzImage-c0a572d9.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/d0602a911ff3/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+47c7e14e1bd09234d0ad@syzkaller.appspotmail.com
REISERFS (device loop0): Using r5 hash to sort names
REISERFS (device loop0): using 3.5.x disk format
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
======================================================
WARNING: possible circular locking dependency detected
6.4.0-syzkaller-00082-gc0a572d9d32f #0 Not tainted
------------------------------------------------------
syz-executor281/5085 is trying to acquire lock:
ffff88807d74e090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock_nested+0x69/0xe0 fs/reiserfs/lock.c:78
but task is already holding lock:
ffff888070c6e7e0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:833 [inline]
ffff888070c6e7e0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: page_cache_ra_unbounded+0x153/0x5e0 mm/readahead.c:226
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (mapping.invalidate_lock#3){.+.+}-{3:3}:
down_read+0x9c/0x480 kernel/locking/rwsem.c:1520
filemap_invalidate_lock_shared include/linux/fs.h:833 [inline]
page_cache_ra_unbounded+0x153/0x5e0 mm/readahead.c:226
do_page_cache_ra mm/readahead.c:300 [inline]
page_cache_ra_order+0x6ec/0xa00 mm/readahead.c:560
do_sync_mmap_readahead mm/filemap.c:3193 [inline]
filemap_fault+0x1572/0x24c0 mm/filemap.c:3285
__do_fault+0x107/0x600 mm/memory.c:4176
do_shared_fault mm/memory.c:4585 [inline]
do_fault mm/memory.c:4663 [inline]
do_pte_missing mm/memory.c:3647 [inline]
handle_pte_fault mm/memory.c:4947 [inline]
__handle_mm_fault+0x24c9/0x41c0 mm/memory.c:5089
handle_mm_fault+0x2a7/0x9e0 mm/memory.c:5243
do_user_addr_fault+0x51a/0x1210 arch/x86/mm/fault.c:1440
handle_page_fault arch/x86/mm/fault.c:1534 [inline]
exc_page_fault+0x98/0x170 arch/x86/mm/fault.c:1590
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
__put_user_4+0x11/0x20 arch/x86/lib/putuser.S:89
reiserfs_ioctl+0x20d/0x330 fs/reiserfs/ioctl.c:96
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl fs/ioctl.c:856 [inline]
__x64_sys_ioctl+0x19d/0x210 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #0 (&sbi->lock){+.+.}-{3:3}:
check_prev_add kernel/locking/lockdep.c:3113 [inline]
check_prevs_add kernel/locking/lockdep.c:3232 [inline]
validate_chain kernel/locking/lockdep.c:3847 [inline]
__lock_acquire+0x2fcd/0x5f30 kernel/locking/lockdep.c:5088
lock_acquire kernel/locking/lockdep.c:5705 [inline]
lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5670
__mutex_lock_common kernel/locking/mutex.c:603 [inline]
__mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
reiserfs_write_lock_nested+0x69/0xe0 fs/reiserfs/lock.c:78
reiserfs_cond_resched fs/reiserfs/reiserfs.h:849 [inline]
reiserfs_cond_resched fs/reiserfs/reiserfs.h:842 [inline]
search_by_key+0x2452/0x3b60 fs/reiserfs/stree.c:712
search_for_position_by_key+0xcf/0x1180 fs/reiserfs/stree.c:874
_get_block_create_0+0x23f/0x1a70 fs/reiserfs/inode.c:305
reiserfs_get_block+0x244f/0x4100 fs/reiserfs/inode.c:695
do_mpage_readpage+0x768/0x1960 fs/mpage.c:234
mpage_readahead+0x344/0x580 fs/mpage.c:382
read_pages+0x1a2/0xd40 mm/readahead.c:161
page_cache_ra_unbounded+0x477/0x5e0 mm/readahead.c:270
do_page_cache_ra mm/readahead.c:300 [inline]
page_cache_ra_order+0x6ec/0xa00 mm/readahead.c:560
do_sync_mmap_readahead mm/filemap.c:3193 [inline]
filemap_fault+0x1572/0x24c0 mm/filemap.c:3285
__do_fault+0x107/0x600 mm/memory.c:4176
do_shared_fault mm/memory.c:4585 [inline]
do_fault mm/memory.c:4663 [inline]
do_pte_missing mm/memory.c:3647 [inline]
handle_pte_fault mm/memory.c:4947 [inline]
__handle_mm_fault+0x24c9/0x41c0 mm/memory.c:5089
handle_mm_fault+0x2a7/0x9e0 mm/memory.c:5243
do_user_addr_fault+0x51a/0x1210 arch/x86/mm/fault.c:1440
handle_page_fault arch/x86/mm/fault.c:1534 [inline]
exc_page_fault+0x98/0x170 arch/x86/mm/fault.c:1590
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
__put_user_4+0x11/0x20 arch/x86/lib/putuser.S:89
reiserfs_ioctl+0x20d/0x330 fs/reiserfs/ioctl.c:96
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl fs/ioctl.c:856 [inline]
__x64_sys_ioctl+0x19d/0x210 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
rlock(mapping.invalidate_lock#3);
lock(&sbi->lock);
lock(mapping.invalidate_lock#3);
lock(&sbi->lock);
*** DEADLOCK ***
1 lock held by syz-executor281/5085:
#0: ffff888070c6e7e0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:833 [inline]
#0: ffff888070c6e7e0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: page_cache_ra_unbounded+0x153/0x5e0 mm/readahead.c:226
stack backtrace:
CPU: 1 PID: 5085 Comm: syz-executor281 Not tainted 6.4.0-syzkaller-00082-gc0a572d9d32f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2188
check_prev_add kernel/locking/lockdep.c:3113 [inline]
check_prevs_add kernel/locking/lockdep.c:3232 [inline]
validate_chain kernel/locking/lockdep.c:3847 [inline]
__lock_acquire+0x2fcd/0x5f30 kernel/locking/lockdep.c:5088
lock_acquire kernel/locking/lockdep.c:5705 [inline]
lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5670
__mutex_lock_common kernel/locking/mutex.c:603 [inline]
__mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
reiserfs_write_lock_nested+0x69/0xe0 fs/reiserfs/lock.c:78
reiserfs_cond_resched fs/reiserfs/reiserfs.h:849 [inline]
reiserfs_cond_resched fs/reiserfs/reiserfs.h:842 [inline]
search_by_key+0x2452/0x3b60 fs/reiserfs/stree.c:712
search_for_position_by_key+0xcf/0x1180 fs/reiserfs/stree.c:874
_get_block_create_0+0x23f/0x1a70 fs/reiserfs/inode.c:305
reiserfs_get_block+0x244f/0x4100 fs/reiserfs/inode.c:695
do_mpage_readpage+0x768/0x1960 fs/mpage.c:234
mpage_readahead+0x344/0x580 fs/mpage.c:382
read_pages+0x1a2/0xd40 mm/readahead.c:161
page_cache_ra_unbounded+0x477/0x5e0 mm/readahead.c:270
do_page_cache_ra mm/readahead.c:300 [inline]
page_cache_ra_order+0x6ec/0xa00 mm/readahead.c:560
do_sync_mmap_readahead mm/filemap.c:3193 [inline]
filemap_fault+0x1572/0x24c0 mm/filemap.c:3285
__do_fault+0x107/0x600 mm/memory.c:4176
do_shared_fault mm/memory.c:4585 [inline]
do_fault mm/memory.c:4663 [inline]
do_pte_missing mm/memory.c:3647 [inline]
handle_pte_fault mm/memory.c:4947 [inline]
__handle_mm_fault+0x24c9/0x41c0 mm/memory.c:5089
handle_mm_fault+0x2a7/0x9e0 mm/memory.c:5243
do_user_addr_fault+0x51a/0x1210 arch/x86/mm/fault.c:1440
handle_page_fault arch/x86/mm/fault.c:1534 [inline]
exc_page_fault+0x98/0x170 arch/x86/mm/fault.c:1590
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0010:__put_user_4+0x11/0x20 arch/x86/lib/putuser.S:91
Code: fa 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 cb 48 c1 fb 3f 48 09 d9 0f 01 cb <89> 01 31 c9 0f 01 ca c3 0f 1f 80 00 00 00 00 f3 0f 1e fa f3 0f 1e
RSP: 0018:ffffc90004217ec0 EFLAGS: 00050206
RAX: 0000000000000002 RBX: 0000000000000000 RCX: 0000000020000000
RDX: 1ffff1100e18dd2b RSI: ffffffff82245cf8 RDI: ffff888070c6e958
RBP: ffffc90004217ef8 R08: 0000000000000001 R09: ffffffff8e7a9657
R10: fffffbfff1cf52ca R11: 0000000000000001 R12: ffff888070c6e4f0
R13: 0000000020000000 R14: ffff888070c6e518 R15: ffff88807bc6ec80
reiserfs_ioctl+0x20d/0x330 fs/reiserfs/ioctl.c:96
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl fs/ioctl.c:856 [inline]
__x64_sys_ioctl+0x19d/0x210 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f934c6b1649
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 01 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe3f7edce8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000000cee5 RCX: 00007f934c6b1649
RDX: 0000000020000000 RSI: 0000000080087601 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe3f7edd1c
R13: 00007ffe3f7edd50 R14: 00007ffe3f7edd30 R15: 000000000000002a
</TASK>
----------------
Code disassembly (best guess):
0: fa cli
1: 0f 01 cb stac
4: 66 89 01 mov %ax,(%rcx)
7: 31 c9 xor %ecx,%ecx
9: 0f 01 ca clac
c: c3 retq
d: 66 66 2e 0f 1f 84 00 data16 nopw %cs:0x0(%rax,%rax,1)
14: 00 00 00 00
18: 90 nop
19: f3 0f 1e fa endbr64
1d: 48 89 cb mov %rcx,%rbx
20: 48 c1 fb 3f sar $0x3f,%rbx
24: 48 09 d9 or %rbx,%rcx
27: 0f 01 cb stac
* 2a: 89 01 mov %eax,(%rcx) <-- trapping instruction
2c: 31 c9 xor %ecx,%ecx
2e: 0f 01 ca clac
31: c3 retq
32: 0f 1f 80 00 00 00 00 nopl 0x0(%rax)
39: f3 0f 1e fa endbr64
3d: f3 repz
3e: 0f .byte 0xf
3f: 1e (bad)
---
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] 134+ messages in thread
* Re: [syzbot]
2022-12-21 8:15 [syzbot] possible deadlock in page_cache_ra_unbounded syzbot
2023-06-26 23:27 ` [syzbot] [reiserfs?] " syzbot
@ 2025-01-08 16:11 ` syzbot
2025-02-20 16:20 ` [syzbot] [mm] [fs] possible deadlock in page_cache_ra_unbounded syzbot
2 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-01-08 16: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:
Author: nogikh@google.com
#syz set subsystems: mm, fs
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot] [mm] [fs] possible deadlock in page_cache_ra_unbounded
2022-12-21 8:15 [syzbot] possible deadlock in page_cache_ra_unbounded syzbot
2023-06-26 23:27 ` [syzbot] [reiserfs?] " syzbot
2025-01-08 16:11 ` [syzbot] syzbot
@ 2025-02-20 16:20 ` syzbot
2025-02-21 14:56 ` Jan Kara
2 siblings, 1 reply; 134+ messages in thread
From: syzbot @ 2025-02-20 16:20 UTC (permalink / raw)
To: akpm, axboe, brauner, jack, linux-fsdevel, linux-kernel,
linux-mm, reiserfs-devel, syzkaller-bugs, willy
syzbot suspects this issue was fixed by commit:
commit 6f861765464f43a71462d52026fbddfc858239a5
Author: Jan Kara <jack@suse.cz>
Date: Wed Nov 1 17:43:10 2023 +0000
fs: Block writes to mounted block devices
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16e867f8580000
start commit: 861deac3b092 Linux 6.7-rc7
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=e1e118a9228c45d7
dashboard link: https://syzkaller.appspot.com/bug?extid=47c7e14e1bd09234d0ad
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=100b9595e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1415ff9ee80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs: Block writes to mounted block devices
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot] [mm] [fs] possible deadlock in page_cache_ra_unbounded
2025-02-20 16:20 ` [syzbot] [mm] [fs] possible deadlock in page_cache_ra_unbounded syzbot
@ 2025-02-21 14:56 ` Jan Kara
0 siblings, 0 replies; 134+ messages in thread
From: Jan Kara @ 2025-02-21 14:56 UTC (permalink / raw)
To: syzbot
Cc: akpm, axboe, brauner, jack, linux-fsdevel, linux-kernel,
linux-mm, reiserfs-devel, syzkaller-bugs, willy
On Thu 20-02-25 08:20:02, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 6f861765464f43a71462d52026fbddfc858239a5
> Author: Jan Kara <jack@suse.cz>
> Date: Wed Nov 1 17:43:10 2023 +0000
>
> fs: Block writes to mounted block devices
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16e867f8580000
> start commit: 861deac3b092 Linux 6.7-rc7
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=e1e118a9228c45d7
> dashboard link: https://syzkaller.appspot.com/bug?extid=47c7e14e1bd09234d0ad
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=100b9595e80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1415ff9ee80000
>
> If the result looks correct, please mark the issue as fixed by replying with:
Makes sense:
#syz fix: fs: Block writes to mounted block devices
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-06-10 19:15 [syzbot] [bcachefs?] divide error in bch2_sb_members_v2_to_text syzbot
@ 2025-06-19 21:00 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-06-19 21:00 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Don't trust sb->nr_devices in members_to_text()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-06-08 5:52 [syzbot] [bcachefs?] kernel BUG in vfs_get_tree (2) syzbot
@ 2025-06-19 20:57 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-06-19 20:57 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Call bch2_fs_start before getting vfs superblock
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-05-31 15:09 [syzbot] [bcachefs?] WARNING in lookup_object_or_alloc syzbot
@ 2025-06-19 20:54 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-06-19 20:54 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Don't put rhashtable on stack
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-06-12 7:52 [syzbot] [bcachefs?] WARNING in __init_work (2) syzbot
@ 2025-06-19 20:54 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-06-19 20:54 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Don't put rhashtable on stack
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-07-13 22:54 [syzbot] [bpf?] [trace?] possible deadlock in console_flush_all (3) syzbot
@ 2025-06-19 20:48 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-06-19 20: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix possible console lock involved deadlock
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-04-28 17:04 [syzbot] [bcachefs?] UBSAN: array-index-out-of-bounds in bch2_sb_downgrade_update syzbot
@ 2025-06-08 16:01 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-06-08 16:01 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix downgrade_table_extra()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-05-26 8:50 [syzbot] [bcachefs?] WARNING in rhashtable_init_noprof syzbot
@ 2025-06-08 15:41 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-06-08 15: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Don't put rhashtable on stack
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-05-26 10:41 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_sb_members_v2_to_text syzbot
@ 2025-06-08 15:33 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-06-08 15: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Don't trust sb->nr_devices in members_to_text()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-04-08 11:53 [syzbot] [bcachefs?] WARNING in bch2_dev_free syzbot
@ 2025-04-18 0:37 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-18 0:37 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Prevent granting write refs when filesystem is read-only
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-23 6:02 [syzbot] linux-next build error (20) syzbot
@ 2025-04-14 14:48 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-14 14: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:
Author: nogikh@google.com
The bug was fixed with a different commit than the recorded [PATCH] discussion.
Close it so that it may be reopened the next time we face a linux next
build problem.
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-17 11:55 [syzbot] [usb?] KMSAN: uninit-value in mii_nway_restart (2) syzbot
2025-02-17 20:59 ` [syzbot] syzbot
@ 2025-04-11 12:15 ` syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-11 12: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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
` (6 preceding siblings ...)
2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
@ 2025-04-07 14:17 ` Arnaud Lecomte
7 siblings, 0 replies; 134+ messages in thread
From: Arnaud Lecomte @ 2025-04-07 14:17 UTC (permalink / raw)
To: syzbot+29fc8991b0ecb186cf40
Cc: andrew+netdev, davem, edumazet, kuba, linux-kernel, linux-ppp,
netdev, pabeni, syzkaller-bugs
Author: contact@arnaud-lcm.com
#syz test
diff --git a/drivers/net/ppp/ppp_synctty.c b/drivers/net/ppp/ppp_synctty.c
index 644e99fc3623..520d895acc60 100644
--- a/drivers/net/ppp/ppp_synctty.c
+++ b/drivers/net/ppp/ppp_synctty.c
@@ -506,6 +506,11 @@ ppp_sync_txmunge(struct syncppp *ap, struct sk_buff *skb)
unsigned char *data;
int islcp;
+ /* Ensure we can safely access protocol field and LCP code */
+ if (!skb || !pskb_may_pull(skb, 3)) {
+ kfree_skb(skb);
+ return NULL;
+ }
data = skb->data;
proto = get_unaligned_be16(data);
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
@ 2025-04-07 14:17 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-07 14:17 UTC (permalink / raw)
To: contact
Cc: andrew, contact, davem, edumazet, kuba, linux-kernel, linux-ppp,
netdev, pabeni, syzkaller-bugs
> Author: contact@arnaud-lcm.com
>
> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
want either no args or 2 args (repo, branch), got 5
>
> diff --git a/drivers/net/ppp/ppp_synctty.c b/drivers/net/ppp/ppp_synctty.c
> index 644e99fc3623..520d895acc60 100644
> --- a/drivers/net/ppp/ppp_synctty.c
> +++ b/drivers/net/ppp/ppp_synctty.c
> @@ -506,6 +506,11 @@ ppp_sync_txmunge(struct syncppp *ap, struct sk_buff *skb)
> unsigned char *data;
> int islcp;
>
> + /* Ensure we can safely access protocol field and LCP code */
> + if (!skb || !pskb_may_pull(skb, 3)) {
> + kfree_skb(skb);
> + return NULL;
> + }
> data = skb->data;
> proto = get_unaligned_be16(data);
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
` (5 preceding siblings ...)
2025-04-07 14:06 ` [syzbot] Arnaud Lecomte
@ 2025-04-07 14:17 ` Arnaud Lecomte
2025-04-07 14:17 ` [syzbot] syzbot
2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
7 siblings, 1 reply; 134+ messages in thread
From: Arnaud Lecomte @ 2025-04-07 14:17 UTC (permalink / raw)
To: syzbot+29fc8991b0ecb186cf40
Cc: andrew+netdev, davem, edumazet, kuba, linux-kernel, linux-ppp,
netdev, pabeni, syzkaller-bugs
Author: contact@arnaud-lcm.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
diff --git a/drivers/net/ppp/ppp_synctty.c b/drivers/net/ppp/ppp_synctty.c
index 644e99fc3623..520d895acc60 100644
--- a/drivers/net/ppp/ppp_synctty.c
+++ b/drivers/net/ppp/ppp_synctty.c
@@ -506,6 +506,11 @@ ppp_sync_txmunge(struct syncppp *ap, struct sk_buff *skb)
unsigned char *data;
int islcp;
+ /* Ensure we can safely access protocol field and LCP code */
+ if (!skb || !pskb_may_pull(skb, 3)) {
+ kfree_skb(skb);
+ return NULL;
+ }
data = skb->data;
proto = get_unaligned_be16(data);
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
` (4 preceding siblings ...)
2025-02-15 19:35 ` [syzbot] syzbot
@ 2025-04-07 14:06 ` Arnaud Lecomte
2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
7 siblings, 0 replies; 134+ messages in thread
From: Arnaud Lecomte @ 2025-04-07 14:06 UTC (permalink / raw)
To: syzbot+29fc8991b0ecb186cf40
Cc: andrew+netdev, davem, edumazet, kuba, linux-kernel, linux-ppp,
netdev, pabeni, syzkaller-bugs
#syz test: https://github.com/ArnaudLcm/linux bounds-checking-txmung
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-03-30 16:49 [syzbot] [pci?] upstream test error: BUG: unable to handle kernel NULL pointer dereference in msix_prepare_msi_desc syzbot
@ 2025-04-03 7:06 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-03 7:06 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:
Author: nogikh@google.com
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-03-30 10:15 [syzbot] [pci?] upstream test error: general protection fault in msix_prepare_msi_desc syzbot
@ 2025-04-03 7:06 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-03 7:06 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:
Author: nogikh@google.com
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-03-31 2:14 [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in __kfifo_alloc syzbot
2025-04-01 10:18 ` [syzbot] syzbot
2025-04-01 10:24 ` [syzbot] syzbot
@ 2025-04-01 11:04 ` syzbot
2 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 11:04 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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-03-31 2:14 [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in __kfifo_alloc syzbot
2025-04-01 10:18 ` [syzbot] syzbot
@ 2025-04-01 10:24 ` syzbot
2025-04-01 11:04 ` [syzbot] syzbot
2 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 10:24 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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-03-31 2:14 [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in __kfifo_alloc syzbot
@ 2025-04-01 10:18 ` syzbot
2025-04-01 10:24 ` [syzbot] syzbot
2025-04-01 11:04 ` [syzbot] syzbot
2 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 10:18 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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-03-31 14:06 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_copygc (2) syzbot
@ 2025-04-01 4:10 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4: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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Eliminate padding in move_bucket_key
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-11 0:28 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_check_topology syzbot
@ 2025-04-01 4:10 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4: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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-22 18:44 [syzbot] [bcachefs?] KMSAN: uninit-value in rw_aux_tree_set (2) syzbot
@ 2025-04-01 4:09 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:09 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-26 0:00 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_trans_start_alloc_update syzbot
@ 2025-04-01 4:08 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:08 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-19 7:33 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_inode_v3_validate syzbot
@ 2025-04-01 4:08 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:08 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-12-13 7:56 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_xattr_validate syzbot
2025-04-01 4:06 ` [syzbot] syzbot
@ 2025-04-01 4:07 ` syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:07 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-17 8:54 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_iter_init (2) syzbot
@ 2025-04-01 4:07 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:07 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-12-15 8:10 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_checksum_update (2) syzbot
@ 2025-04-01 4:06 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:06 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-12-13 7:56 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_xattr_validate syzbot
@ 2025-04-01 4:06 ` syzbot
2025-04-01 4:07 ` [syzbot] syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:06 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-06 13:58 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bucket_alloc_early syzbot
@ 2025-04-01 4:05 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4: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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-30 19:55 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_dirent_validate syzbot
@ 2025-04-01 4:04 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:04 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-12-19 10:14 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_dirent_rename (2) syzbot
@ 2025-04-01 4:04 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:04 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-12-04 17:36 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_dev_freespace_init syzbot
@ 2025-04-01 4:03 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:03 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-12-13 19:13 [syzbot] [bcachefs?] KMSAN: uninit-value in __build_ro_aux_tree syzbot
@ 2025-04-01 4:03 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:03 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-12-24 14:42 [syzbot] [bcachefs?] KMSAN: uninit-value in __bch2_bkey_cmp_left_packed syzbot
@ 2025-04-01 4:02 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:02 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-29 16:59 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bkey_val_validate syzbot
@ 2025-04-01 4:02 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:02 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-12-01 8:34 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bkey_ptrs_validate syzbot
@ 2025-04-01 4:02 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:02 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-27 18:59 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bkey_cmp_packed_inlined (2) syzbot
@ 2025-04-01 4:01 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:01 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-17 8:54 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_alloc_v4_validate (2) syzbot
@ 2025-04-01 4:00 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 4:00 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-12-01 9:40 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_get syzbot
@ 2025-04-01 3:59 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 3:59 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-01-11 13:37 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_readdir (2) syzbot
@ 2025-04-01 3:59 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 3:59 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-01-01 20:55 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_inode_unpack (2) syzbot
@ 2025-04-01 3:58 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 3: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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-01-03 1:56 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_trans_start_alloc_update_noupdate syzbot
@ 2025-04-01 3:58 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 3: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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-01-29 9:17 [syzbot] [bcachefs?] KMSAN: uninit-value in btree_interior_update_work syzbot
@ 2025-04-01 3:57 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 3:57 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Fix a KMSAN splat in btree_update_nodes_written()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-04 15:33 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_ptr_v2_validate syzbot
@ 2025-04-01 3:56 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 3:56 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Disable asm memcpys when kmsan enabled
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-03-09 4:20 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_extent_crc_append (2) syzbot
@ 2025-04-01 3:55 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-04-01 3: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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Fix kmsan warnings in bch2_extent_crc_pack()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-17 11:55 [syzbot] [usb?] KMSAN: uninit-value in mii_nway_restart (2) syzbot
@ 2025-02-17 20:59 ` syzbot
2025-04-11 12:15 ` [syzbot] syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-17 20:59 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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-17 11:55 [syzbot] [can?] WARNING in ucan_probe syzbot
@ 2025-02-17 17:59 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-17 17:59 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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
` (3 preceding siblings ...)
2025-02-15 18:42 ` [syzbot] syzbot
@ 2025-02-15 19:35 ` syzbot
2025-04-07 14:06 ` [syzbot] Arnaud Lecomte
` (2 subsequent siblings)
7 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-15 19:35 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:
Author: purvayeshi550@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
` (2 preceding siblings ...)
2025-02-15 14:31 ` [syzbot] syzbot
@ 2025-02-15 18:42 ` syzbot
2025-02-15 19:35 ` [syzbot] syzbot
` (3 subsequent siblings)
7 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-15 18:42 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:
Author: purvayeshi550@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
2025-02-15 7:58 ` [syzbot] syzbot
2025-02-15 12:33 ` [syzbot] syzbot
@ 2025-02-15 14:31 ` syzbot
2025-02-15 18:42 ` [syzbot] syzbot
` (4 subsequent siblings)
7 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-15 14:31 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:
Author: purvayeshi550@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
2025-02-15 7:58 ` [syzbot] syzbot
@ 2025-02-15 12:33 ` syzbot
2025-02-15 14:31 ` [syzbot] syzbot
` (5 subsequent siblings)
7 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-15 12: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:
Author: purvayeshi550@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
@ 2025-02-15 7:58 ` syzbot
2025-02-15 12:33 ` [syzbot] syzbot
` (6 subsequent siblings)
7 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-15 7: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:
Author: purvayeshi550@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-12 13:41 [syzbot] [modules?] KMSAN: uninit-value in __request_module (6) syzbot
2025-02-13 14:21 ` [syzbot] syzbot
@ 2025-02-13 18:22 ` syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-13 18:22 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:
Author: purvayeshi550@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-12 13:41 [syzbot] [modules?] KMSAN: uninit-value in __request_module (6) syzbot
@ 2025-02-13 14:21 ` syzbot
2025-02-13 18:22 ` [syzbot] syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-13 14:21 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:
Author: purvayeshi550@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-12 10:57 [syzbot] [jfs?] KASAN: slab-out-of-bounds Read in ea_get (4) syzbot
@ 2025-02-12 22:56 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-12 22:56 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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-09 5:48 [syzbot] [isofs?] KMSAN: uninit-value in isofs_readdir syzbot
2025-02-09 23:50 ` [syzbot] syzbot
@ 2025-02-11 1:00 ` syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-11 1:00 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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-02-09 5:48 [syzbot] [isofs?] KMSAN: uninit-value in isofs_readdir syzbot
@ 2025-02-09 23:50 ` syzbot
2025-02-11 1:00 ` [syzbot] syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-09 23:50 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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-27 0:00 [syzbot] upstream build error (22) syzbot
@ 2025-02-03 12:55 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-02-03 12: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:
Author: nogikh@google.com
All the previous reasons for build breakages are no longer relevant.
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-01-17 6:14 [syzbot] [usb?] general protection fault in status_show syzbot
@ 2025-01-17 15:41 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-01-17 15: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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-01-12 6:45 [syzbot] [iommu?] UBSAN: shift-out-of-bounds in iova_bitmap_alloc syzbot
@ 2025-01-12 11:58 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-01-12 11: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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-01-11 0:40 [syzbot] [usb?] general protection fault in qt2_read_bulk_callback syzbot
@ 2025-01-11 17:19 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2025-01-11 17: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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-01-02 14:45 [syzbot] [f2fs?] KASAN: slab-out-of-bounds Read in f2fs_getxattr syzbot
2025-01-07 22:19 ` [syzbot] syzbot
@ 2025-01-08 14:13 ` syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2025-01-08 14:13 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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2025-01-02 14:45 [syzbot] [f2fs?] KASAN: slab-out-of-bounds Read in f2fs_getxattr syzbot
@ 2025-01-07 22:19 ` syzbot
2025-01-08 14:13 ` [syzbot] syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2025-01-07 22: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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-12-25 2:26 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in force_devcd_write syzbot
@ 2024-12-26 3:43 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-12-26 3:43 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:
Author: mazin@getstate.dev
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-12-24 6:38 [syzbot] [input?] KASAN: null-ptr-deref Write in input_ff_create syzbot
@ 2024-12-25 16:44 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-12-25 16:44 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:
Author: qasdev00@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-07-24 8:59 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in mgmt_remove_adv_monitor_sync syzbot
2024-12-05 1:58 ` [syzbot] syzbot
@ 2024-12-23 22:19 ` syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2024-12-23 22: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:
Author: mazin@getstate.dev
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-22 14:42 [syzbot] [netfilter?] KMSAN: uninit-value in ip6table_mangle_hook (3) syzbot
2024-12-14 22:16 ` [syzbot] syzbot
2024-12-14 22:21 ` [syzbot] syzbot
@ 2024-12-15 2:34 ` syzbot
2 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-12-15 2: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:
Author: mazin@getstate.dev
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-22 14:42 [syzbot] [netfilter?] KMSAN: uninit-value in ip6table_mangle_hook (3) syzbot
2024-12-14 22:16 ` [syzbot] syzbot
@ 2024-12-14 22:21 ` syzbot
2024-12-15 2:34 ` [syzbot] syzbot
2 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-12-14 22:21 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:
Author: mazin@getstate.dev
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-22 14:42 [syzbot] [netfilter?] KMSAN: uninit-value in ip6table_mangle_hook (3) syzbot
@ 2024-12-14 22:16 ` syzbot
2024-12-14 22:21 ` [syzbot] syzbot
2024-12-15 2:34 ` [syzbot] syzbot
2 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-12-14 22:16 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:
Author: mazin@getstate.dev
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-07-24 8:59 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in mgmt_remove_adv_monitor_sync syzbot
@ 2024-12-05 1:58 ` syzbot
2024-12-23 22:19 ` [syzbot] syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2024-12-05 1: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:
Author: mazin@getstate.dev
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-25 13:05 [syzbot] [bcachefs?] kernel BUG in bch2_evacuate_bucket syzbot
@ 2024-11-29 0:39 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-29 0:39 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Kill bch2_get_next_backpointer()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-12 3:25 [syzbot] [bcachefs?] possible deadlock in bch2_alloc_sectors_start_trans syzbot
@ 2024-11-29 0:34 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-29 0: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Don't recurse in check_discard_freespace_key
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-08 15:57 [syzbot] [bcachefs?] kernel BUG in bch2_rechecksum_bio syzbot
@ 2024-11-29 0:32 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-29 0:32 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Check for extent crc uncompressed/compressed size mismatch
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-23 18:30 [syzbot] [bcachefs?] possible deadlock in __bch2_trans_relock syzbot
@ 2024-11-28 23:06 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-28 23:06 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: bch2_trans_relock() is trylock for lockdep
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-07-17 13:39 [syzbot] [bcachefs?] general protection fault in bch2_checksum syzbot
@ 2024-11-28 22:59 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-28 22:59 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: cryptographic MACs on superblock are not (yet?) supported
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-09-18 7:28 [syzbot] [bcachefs?] WARNING in bch2_journal_flush_seq_async syzbot
@ 2024-11-28 22:50 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-28 22:50 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Check for inode journal seq in the future
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-07-10 20:55 [syzbot] [bcachefs?] kernel BUG in bch2_journal_noflush_seq syzbot
@ 2024-11-28 22:12 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-28 22:12 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Check for bucket journal sequence numbers from the future
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-28 9:49 [syzbot] [bcachefs?] kernel BUG in bch2_get_scanned_nodes syzbot
@ 2024-11-28 20:31 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-28 20:31 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: struct bkey_validate_context
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-25 13:28 [syzbot] [bcachefs?] BUG: corrupted list in bch2_btree_and_journal_iter_exit syzbot
@ 2024-11-28 20:12 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-28 20:12 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix journal_iter list corruption
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-06 13:24 [syzbot] [bcachefs?] kernel BUG in bch2_btree_path_traverse_one syzbot
@ 2024-11-28 3:27 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-28 3: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix btree node scan when unknown btree IDs are present
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-25 13:28 [syzbot] [bcachefs?] kernel BUG in bch2_journal_pin_set syzbot
@ 2024-11-28 3:23 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-28 3:23 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Guard against journal seq overflow
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-28 15:49 [syzbot] [bcachefs?] kernel BUG in bch2_btree_write_buffer_flush_locked syzbot
@ 2024-11-28 3:21 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-28 3:21 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Guard against journal seq overflow
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-21 12:40 [syzbot] [bcachefs?] kernel BUG in bch2_btree_node_lock_write syzbot
@ 2024-11-28 3:12 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-28 3:12 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Issue a transaction restart after commit in repair
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-25 3:10 [syzbot] [bcachefs?] kernel BUG in __bch2_journal_pin_put syzbot
@ 2024-11-28 3:00 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-28 3:00 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Guard against journal seq overflow
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-25 6:48 [syzbot] [bcachefs?] general protection fault in bch2_btree_path_traverse_one syzbot
@ 2024-11-27 8:09 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-27 8:09 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Ignore empty btree root journal entries
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-06-14 12:16 [syzbot] [crypto?] [bcachefs?] BUG: unable to handle kernel paging request in crypto_skcipher_encrypt syzbot
@ 2024-11-25 7:19 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-25 7: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Don't try to en/decrypt when encryption not available
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-18 21:41 [syzbot] [bcachefs?] kernel BUG in bch2_bucket_alloc_trans (3) syzbot
@ 2024-11-25 6:54 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-25 6:54 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Kill bch2_bucket_alloc_new_fs()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-22 15:15 [syzbot] [bcachefs?] kernel BUG in bch2_btree_root_read syzbot
@ 2024-11-25 6:53 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-25 6:53 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Kill bch2_bucket_alloc_new_fs()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-03 8:10 [syzbot] [bcachefs?] kernel BUG in __bch2_btree_node_write syzbot
@ 2024-11-25 6:52 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-25 6: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix dup/misordered check in btree node read
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-22 18:44 [syzbot] [bcachefs?] kernel BUG in bch2_btree_pos_to_text (2) syzbot
@ 2024-11-25 3:59 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-25 3:59 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix btree node scan when unknown btree IDs are present
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2020-10-13 17:02 WARNING in drop_nlink (2) syzbot
@ 2024-11-20 15:35 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-20 15:35 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:
Author: nogikh@google.com
There will be no such crash title under the new report extraction rules
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-23 4:12 [syzbot] [bcachefs?] kernel BUG in bch2_ptr_swab syzbot
@ 2024-11-11 21:16 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-11 21:16 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix assertion pop in bch2_ptr_swab()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-07-30 1:14 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in journal_entry_dev_usage_to_text syzbot
@ 2024-11-11 21:03 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-11 21:03 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix journal_entry_dev_usage_to_text() overrun
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-18 7:37 [syzbot] [bcachefs?] kernel BUG in bch2_fs_btree_cache_exit syzbot
@ 2024-11-11 4:46 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-11 4: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: bch2_btree_write_buffer_flush_going_ro()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-24 17:47 [syzbot] [bcachefs?] kernel BUG in bch2_run_recovery_pass syzbot
@ 2024-11-11 4:31 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-11 4:31 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Allow for unknown key types in backpointers fsck
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-23 11:21 [syzbot] [bcachefs?] kernel BUG in bch2_btree_path_level_init (2) syzbot
@ 2024-11-11 3:14 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-11 3:14 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix missing validation for bch_backpointer.level
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-11-09 15:43 [syzbot] [bcachefs?] kernel BUG in __bch2_btree_node_hash_insert syzbot
@ 2024-11-11 3:13 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-11 3:13 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix assertion pop in topology repair
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-27 1:10 [syzbot] [bcachefs?] kernel BUG in bch2_bkey_pack_pos_lossy syzbot
@ 2024-11-08 5:11 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-08 5: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix validate_bset() repair path
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-30 16:39 [syzbot] [bcachefs?] kernel BUG in __bkey_unpack_pos syzbot
@ 2024-11-08 5:02 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-08 5:02 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix validate_bset() repair path
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-21 13:07 [syzbot] [bcachefs?] kernel BUG in bch2_dev_btree_bitmap_mark syzbot
@ 2024-11-08 4:25 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-08 4: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix bch_member.btree_bitmap_shift validation
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-25 6:48 [syzbot] [bcachefs?] kernel BUG in bch2_journal_res_get (2) syzbot
@ 2024-11-08 3:28 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-08 3: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: bch2_btree_write_buffer_flush_going_ro()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-25 6:49 [syzbot] [bcachefs?] kernel BUG in bch2_trans_node_iter_init syzbot
@ 2024-11-08 3:21 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-08 3:21 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Fix missing validation for bch_backpointer.level
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-09-28 2:13 [syzbot] [bcachefs?] kernel BUG in bch2_fs_btree_write_buffer_exit syzbot
@ 2024-11-08 3:04 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-08 3:04 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: bch2_btree_write_buffer_flush_going_ro()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-27 3:54 [syzbot] [bcachefs?] kernel BUG in bch2_inconsistent_error syzbot
@ 2024-11-08 0:48 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-08 0: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Change OPT_STR max to be 1 less than the size of choices array
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-25 6:49 [syzbot] [bcachefs?] kernel BUG in __bch2_bkey_cmp_packed_format_checked syzbot
@ 2024-11-08 0:34 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-08 0: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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: Ancient versions with bad bkey_formats are no longer supported
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-21 4:31 [syzbot] [bcachefs?] kernel BUG in __bch2_trans_commit syzbot
@ 2024-11-08 0:18 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-11-08 0:18 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:
Author: kent.overstreet@linux.dev
#syz fix: bcachefs: -o norecovery now bails out of recovery earlier
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2021-02-01 10:07 BUG: Bad page state (8) syzbot
@ 2024-10-28 14:11 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-10-28 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:
Author: nogikh@google.com
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-23 14:27 [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in validate_sb_layout syzbot
@ 2024-10-26 0:49 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-10-26 0: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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Fix invalid shift in validate_sb_layout()
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-21 6:44 [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in bch2_alloc_to_text syzbot
@ 2024-10-26 0:47 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-10-26 0:47 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: fix shift oob in alloc_lru_idx_fragmentation
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-10-03 17:42 [syzbot] [bcachefs?] possible deadlock in bch2_replicas_entry_validate syzbot
@ 2024-10-16 6:42 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-10-16 6:42 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:
Author: kent.overstreet@linux.dev
#syz fix bcachefs: Fix lockdep splat in bch2_accounting_read
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2020-08-08 21:27 KASAN: use-after-free Read in __queue_work (3) syzbot
@ 2024-09-06 10:40 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-09-06 10:40 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:
Author: nogikh@google.com
#syz invalid
Repro triggers a different kind of problem
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2020-11-21 1:55 INFO: task can't die in shrink_inactive_list (2) syzbot
@ 2024-09-06 10:39 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-09-06 10:39 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:
Author: nogikh@google.com
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2022-09-25 11:18 [syzbot] WARNING in __change_page_attr_set_clr syzbot
@ 2024-09-06 10:39 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-09-06 10:39 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:
Author: nogikh@google.com
#syz invalid
Repro triggers a different problem
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2023-10-16 7:38 [syzbot] [kernel?] KASAN: slab-use-after-free Read in reweight_entity syzbot
@ 2024-09-06 10:38 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-09-06 10:38 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:
Author: nogikh@google.com
#syz invalid
Repro triggers a different kind of an issue
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2023-11-16 11:09 [syzbot] [kernel?] inconsistent lock state in __lock_task_sighand syzbot
@ 2024-09-06 10:37 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-09-06 10:37 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:
Author: nogikh@google.com
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2022-07-12 12:03 [syzbot] inconsistent lock state in find_vmap_area syzbot
@ 2024-09-06 10:36 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-09-06 10: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:
Author: nogikh@google.com
#syz invalid
Repro now triggers a different kind of problem
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2020-08-04 15:46 KASAN: use-after-free Read in __sco_sock_close syzbot
@ 2024-09-06 10:35 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-09-06 10:35 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:
Author: nogikh@google.com
The reproducer now hits
WARNING: CPU: 0 PID: 5640 at net/bluetooth/hci_conn.c:565
hci_conn_timeout+0xfb/0x290 net/bluetooth/hci_conn.c:565
for which we have a separate bug.
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-08-27 2:12 [syzbot] [sound?] WARNING in snd_pcm_open syzbot
@ 2024-09-06 10:33 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-09-06 10: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:
Author: nogikh@google.com
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-01-05 17:32 [syzbot] [net?] memory leak in ___neigh_create (2) syzbot
@ 2024-09-05 11:54 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-09-05 11:54 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:
Author: nogikh@google.com
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2021-02-26 14:48 general protection fault in try_to_wake_up (2) syzbot
@ 2024-07-25 16:29 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-07-25 16:29 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:
Author: axboe@kernel.dk
#syz invalid
--
Jens Axboe
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2022-10-17 7:43 [syzbot] possible deadlock in attr_data_get_block syzbot
@ 2024-07-17 8:19 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-07-17 8: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:
Author: almaz.alexandrovich@paragon-software.com
#syz test: https://github.com/Paragon-Software-Group/linux-ntfs3.git
d57431c6f511bf020e474026d9f3123d7bfbea8c
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2023-06-05 3:53 [syzbot] [ext4?] WARNING: locking bug in ext4_move_extents syzbot
@ 2024-07-03 7:48 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-07-03 7:48 UTC (permalink / raw)
To: linux-kernel
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject:
Author: bottaawesome633@gmail.com
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2024-01-12 20:14 [syzbot] upstream build error (21) syzbot
@ 2024-06-20 8:00 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-06-20 8:00 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:
Author: nogikh@google.com
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
[not found] <mailman.217.1706634262.2961.pvrusb2@isely.net>
@ 2024-02-15 16:26 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2024-02-15 16:26 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:
Author: mazin@getstate.dev
#syz test
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2018-11-24 19:40 WARNING in csum_and_copy_to_iter syzbot
@ 2023-11-24 10:30 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2023-11-24 10: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:
Author: nogikh@google.com
The issue has not been happening for >1800 days.
#syz invalid
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2023-11-15 9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
2023-11-16 2:33 ` [syzbot] syzbot
@ 2023-11-16 3:29 ` syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2023-11-16 3:29 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:
Author: mazinalhaddad05@gmail.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2023-11-15 9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
@ 2023-11-16 2:33 ` syzbot
2023-11-16 3:29 ` [syzbot] syzbot
1 sibling, 0 replies; 134+ messages in thread
From: syzbot @ 2023-11-16 2: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:
Author: mazinalhaddad05@gmail.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
^ permalink raw reply [flat|nested] 134+ messages in thread
* Re: [syzbot]
2022-02-10 19:17 [syzbot] general protection fault in blk_mq_free_rqs syzbot
@ 2023-11-10 18:56 ` syzbot
0 siblings, 0 replies; 134+ messages in thread
From: syzbot @ 2023-11-10 18:56 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:
Author: yuran.pereira@hotmail.com
#syz test: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master
^ permalink raw reply [flat|nested] 134+ messages in thread
end of thread, other threads:[~2025-06-19 21:00 UTC | newest]
Thread overview: 134+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-21 8:15 [syzbot] possible deadlock in page_cache_ra_unbounded syzbot
2023-06-26 23:27 ` [syzbot] [reiserfs?] " syzbot
2025-01-08 16:11 ` [syzbot] syzbot
2025-02-20 16:20 ` [syzbot] [mm] [fs] possible deadlock in page_cache_ra_unbounded syzbot
2025-02-21 14:56 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2025-06-12 7:52 [syzbot] [bcachefs?] WARNING in __init_work (2) syzbot
2025-06-19 20:54 ` [syzbot] syzbot
2025-06-10 19:15 [syzbot] [bcachefs?] divide error in bch2_sb_members_v2_to_text syzbot
2025-06-19 21:00 ` [syzbot] syzbot
2025-06-08 5:52 [syzbot] [bcachefs?] kernel BUG in vfs_get_tree (2) syzbot
2025-06-19 20:57 ` [syzbot] syzbot
2025-05-31 15:09 [syzbot] [bcachefs?] WARNING in lookup_object_or_alloc syzbot
2025-06-19 20:54 ` [syzbot] syzbot
2025-05-26 10:41 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_sb_members_v2_to_text syzbot
2025-06-08 15:33 ` [syzbot] syzbot
2025-05-26 8:50 [syzbot] [bcachefs?] WARNING in rhashtable_init_noprof syzbot
2025-06-08 15:41 ` [syzbot] syzbot
2025-04-28 17:04 [syzbot] [bcachefs?] UBSAN: array-index-out-of-bounds in bch2_sb_downgrade_update syzbot
2025-06-08 16:01 ` [syzbot] syzbot
2025-04-08 11:53 [syzbot] [bcachefs?] WARNING in bch2_dev_free syzbot
2025-04-18 0:37 ` [syzbot] syzbot
2025-03-31 14:06 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_copygc (2) syzbot
2025-04-01 4:10 ` [syzbot] syzbot
2025-03-31 2:14 [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in __kfifo_alloc syzbot
2025-04-01 10:18 ` [syzbot] syzbot
2025-04-01 10:24 ` [syzbot] syzbot
2025-04-01 11:04 ` [syzbot] syzbot
2025-03-30 16:49 [syzbot] [pci?] upstream test error: BUG: unable to handle kernel NULL pointer dereference in msix_prepare_msi_desc syzbot
2025-04-03 7:06 ` [syzbot] syzbot
2025-03-30 10:15 [syzbot] [pci?] upstream test error: general protection fault in msix_prepare_msi_desc syzbot
2025-04-03 7:06 ` [syzbot] syzbot
2025-03-09 4:20 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_extent_crc_append (2) syzbot
2025-04-01 3:55 ` [syzbot] syzbot
2025-02-23 6:02 [syzbot] linux-next build error (20) syzbot
2025-04-14 14:48 ` [syzbot] syzbot
2025-02-17 11:55 [syzbot] [can?] WARNING in ucan_probe syzbot
2025-02-17 17:59 ` [syzbot] syzbot
2025-02-17 11:55 [syzbot] [usb?] KMSAN: uninit-value in mii_nway_restart (2) syzbot
2025-02-17 20:59 ` [syzbot] syzbot
2025-04-11 12:15 ` [syzbot] syzbot
2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
2025-02-15 7:58 ` [syzbot] syzbot
2025-02-15 12:33 ` [syzbot] syzbot
2025-02-15 14:31 ` [syzbot] syzbot
2025-02-15 18:42 ` [syzbot] syzbot
2025-02-15 19:35 ` [syzbot] syzbot
2025-04-07 14:06 ` [syzbot] Arnaud Lecomte
2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
2025-04-07 14:17 ` [syzbot] syzbot
2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
2025-02-12 13:41 [syzbot] [modules?] KMSAN: uninit-value in __request_module (6) syzbot
2025-02-13 14:21 ` [syzbot] syzbot
2025-02-13 18:22 ` [syzbot] syzbot
2025-02-12 10:57 [syzbot] [jfs?] KASAN: slab-out-of-bounds Read in ea_get (4) syzbot
2025-02-12 22:56 ` [syzbot] syzbot
2025-02-09 5:48 [syzbot] [isofs?] KMSAN: uninit-value in isofs_readdir syzbot
2025-02-09 23:50 ` [syzbot] syzbot
2025-02-11 1:00 ` [syzbot] syzbot
2025-02-04 15:33 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_ptr_v2_validate syzbot
2025-04-01 3:56 ` [syzbot] syzbot
2025-01-29 9:17 [syzbot] [bcachefs?] KMSAN: uninit-value in btree_interior_update_work syzbot
2025-04-01 3:57 ` [syzbot] syzbot
2025-01-17 6:14 [syzbot] [usb?] general protection fault in status_show syzbot
2025-01-17 15:41 ` [syzbot] syzbot
2025-01-12 6:45 [syzbot] [iommu?] UBSAN: shift-out-of-bounds in iova_bitmap_alloc syzbot
2025-01-12 11:58 ` [syzbot] syzbot
2025-01-11 13:37 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_readdir (2) syzbot
2025-04-01 3:59 ` [syzbot] syzbot
2025-01-11 0:40 [syzbot] [usb?] general protection fault in qt2_read_bulk_callback syzbot
2025-01-11 17:19 ` [syzbot] syzbot
2025-01-03 1:56 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_trans_start_alloc_update_noupdate syzbot
2025-04-01 3:58 ` [syzbot] syzbot
2025-01-02 14:45 [syzbot] [f2fs?] KASAN: slab-out-of-bounds Read in f2fs_getxattr syzbot
2025-01-07 22:19 ` [syzbot] syzbot
2025-01-08 14:13 ` [syzbot] syzbot
2025-01-01 20:55 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_inode_unpack (2) syzbot
2025-04-01 3:58 ` [syzbot] syzbot
2024-12-25 2:26 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in force_devcd_write syzbot
2024-12-26 3:43 ` [syzbot] syzbot
2024-12-24 14:42 [syzbot] [bcachefs?] KMSAN: uninit-value in __bch2_bkey_cmp_left_packed syzbot
2025-04-01 4:02 ` [syzbot] syzbot
2024-12-24 6:38 [syzbot] [input?] KASAN: null-ptr-deref Write in input_ff_create syzbot
2024-12-25 16:44 ` [syzbot] syzbot
2024-12-19 10:14 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_dirent_rename (2) syzbot
2025-04-01 4:04 ` [syzbot] syzbot
2024-12-15 8:10 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_checksum_update (2) syzbot
2025-04-01 4:06 ` [syzbot] syzbot
2024-12-13 19:13 [syzbot] [bcachefs?] KMSAN: uninit-value in __build_ro_aux_tree syzbot
2025-04-01 4:03 ` [syzbot] syzbot
2024-12-13 7:56 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_xattr_validate syzbot
2025-04-01 4:06 ` [syzbot] syzbot
2025-04-01 4:07 ` [syzbot] syzbot
2024-12-04 17:36 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_dev_freespace_init syzbot
2025-04-01 4:03 ` [syzbot] syzbot
2024-12-01 9:40 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_get syzbot
2025-04-01 3:59 ` [syzbot] syzbot
2024-12-01 8:34 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bkey_ptrs_validate syzbot
2025-04-01 4:02 ` [syzbot] syzbot
2024-11-30 19:55 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_dirent_validate syzbot
2025-04-01 4:04 ` [syzbot] syzbot
2024-11-29 16:59 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bkey_val_validate syzbot
2025-04-01 4:02 ` [syzbot] syzbot
2024-11-28 9:49 [syzbot] [bcachefs?] kernel BUG in bch2_get_scanned_nodes syzbot
2024-11-28 20:31 ` [syzbot] syzbot
2024-11-27 18:59 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bkey_cmp_packed_inlined (2) syzbot
2025-04-01 4:01 ` [syzbot] syzbot
2024-11-27 0:00 [syzbot] upstream build error (22) syzbot
2025-02-03 12:55 ` [syzbot] syzbot
2024-11-26 0:00 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_trans_start_alloc_update syzbot
2025-04-01 4:08 ` [syzbot] syzbot
2024-11-25 13:28 [syzbot] [bcachefs?] BUG: corrupted list in bch2_btree_and_journal_iter_exit syzbot
2024-11-28 20:12 ` [syzbot] syzbot
2024-11-25 13:28 [syzbot] [bcachefs?] kernel BUG in bch2_journal_pin_set syzbot
2024-11-28 3:23 ` [syzbot] syzbot
2024-11-25 13:05 [syzbot] [bcachefs?] kernel BUG in bch2_evacuate_bucket syzbot
2024-11-29 0:39 ` [syzbot] syzbot
2024-11-25 3:10 [syzbot] [bcachefs?] kernel BUG in __bch2_journal_pin_put syzbot
2024-11-28 3:00 ` [syzbot] syzbot
2024-11-22 18:44 [syzbot] [bcachefs?] KMSAN: uninit-value in rw_aux_tree_set (2) syzbot
2025-04-01 4:09 ` [syzbot] syzbot
2024-11-22 18:44 [syzbot] [bcachefs?] kernel BUG in bch2_btree_pos_to_text (2) syzbot
2024-11-25 3:59 ` [syzbot] syzbot
2024-11-22 15:15 [syzbot] [bcachefs?] kernel BUG in bch2_btree_root_read syzbot
2024-11-25 6:53 ` [syzbot] syzbot
2024-11-22 14:42 [syzbot] [netfilter?] KMSAN: uninit-value in ip6table_mangle_hook (3) syzbot
2024-12-14 22:16 ` [syzbot] syzbot
2024-12-14 22:21 ` [syzbot] syzbot
2024-12-15 2:34 ` [syzbot] syzbot
2024-11-21 12:40 [syzbot] [bcachefs?] kernel BUG in bch2_btree_node_lock_write syzbot
2024-11-28 3:12 ` [syzbot] syzbot
2024-11-19 7:33 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_inode_v3_validate syzbot
2025-04-01 4:08 ` [syzbot] syzbot
2024-11-18 21:41 [syzbot] [bcachefs?] kernel BUG in bch2_bucket_alloc_trans (3) syzbot
2024-11-25 6:54 ` [syzbot] syzbot
2024-11-17 8:54 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_alloc_v4_validate (2) syzbot
2025-04-01 4:00 ` [syzbot] syzbot
2024-11-17 8:54 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_iter_init (2) syzbot
2025-04-01 4:07 ` [syzbot] syzbot
2024-11-12 3:25 [syzbot] [bcachefs?] possible deadlock in bch2_alloc_sectors_start_trans syzbot
2024-11-29 0:34 ` [syzbot] syzbot
2024-11-11 0:28 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_check_topology syzbot
2025-04-01 4:10 ` [syzbot] syzbot
2024-11-09 15:43 [syzbot] [bcachefs?] kernel BUG in __bch2_btree_node_hash_insert syzbot
2024-11-11 3:13 ` [syzbot] syzbot
2024-11-08 15:57 [syzbot] [bcachefs?] kernel BUG in bch2_rechecksum_bio syzbot
2024-11-29 0:32 ` [syzbot] syzbot
2024-11-06 13:58 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bucket_alloc_early syzbot
2025-04-01 4:05 ` [syzbot] syzbot
2024-11-06 13:24 [syzbot] [bcachefs?] kernel BUG in bch2_btree_path_traverse_one syzbot
2024-11-28 3:27 ` [syzbot] syzbot
2024-10-30 16:39 [syzbot] [bcachefs?] kernel BUG in __bkey_unpack_pos syzbot
2024-11-08 5:02 ` [syzbot] syzbot
2024-10-28 15:49 [syzbot] [bcachefs?] kernel BUG in bch2_btree_write_buffer_flush_locked syzbot
2024-11-28 3:21 ` [syzbot] syzbot
2024-10-27 3:54 [syzbot] [bcachefs?] kernel BUG in bch2_inconsistent_error syzbot
2024-11-08 0:48 ` [syzbot] syzbot
2024-10-27 1:10 [syzbot] [bcachefs?] kernel BUG in bch2_bkey_pack_pos_lossy syzbot
2024-11-08 5:11 ` [syzbot] syzbot
2024-10-25 6:49 [syzbot] [bcachefs?] kernel BUG in __bch2_bkey_cmp_packed_format_checked syzbot
2024-11-08 0:34 ` [syzbot] syzbot
2024-10-25 6:49 [syzbot] [bcachefs?] kernel BUG in bch2_trans_node_iter_init syzbot
2024-11-08 3:21 ` [syzbot] syzbot
2024-10-25 6:48 [syzbot] [bcachefs?] general protection fault in bch2_btree_path_traverse_one syzbot
2024-11-27 8:09 ` [syzbot] syzbot
2024-10-25 6:48 [syzbot] [bcachefs?] kernel BUG in bch2_journal_res_get (2) syzbot
2024-11-08 3:28 ` [syzbot] syzbot
2024-10-24 17:47 [syzbot] [bcachefs?] kernel BUG in bch2_run_recovery_pass syzbot
2024-11-11 4:31 ` [syzbot] syzbot
2024-10-23 18:30 [syzbot] [bcachefs?] possible deadlock in __bch2_trans_relock syzbot
2024-11-28 23:06 ` [syzbot] syzbot
2024-10-23 14:27 [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in validate_sb_layout syzbot
2024-10-26 0:49 ` [syzbot] syzbot
2024-10-23 11:21 [syzbot] [bcachefs?] kernel BUG in bch2_btree_path_level_init (2) syzbot
2024-11-11 3:14 ` [syzbot] syzbot
2024-10-23 4:12 [syzbot] [bcachefs?] kernel BUG in bch2_ptr_swab syzbot
2024-11-11 21:16 ` [syzbot] syzbot
2024-10-21 13:07 [syzbot] [bcachefs?] kernel BUG in bch2_dev_btree_bitmap_mark syzbot
2024-11-08 4:25 ` [syzbot] syzbot
2024-10-21 6:44 [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in bch2_alloc_to_text syzbot
2024-10-26 0:47 ` [syzbot] syzbot
2024-10-21 4:31 [syzbot] [bcachefs?] kernel BUG in __bch2_trans_commit syzbot
2024-11-08 0:18 ` [syzbot] syzbot
2024-10-18 7:37 [syzbot] [bcachefs?] kernel BUG in bch2_fs_btree_cache_exit syzbot
2024-11-11 4:46 ` [syzbot] syzbot
2024-10-03 17:42 [syzbot] [bcachefs?] possible deadlock in bch2_replicas_entry_validate syzbot
2024-10-16 6:42 ` [syzbot] syzbot
2024-10-03 8:10 [syzbot] [bcachefs?] kernel BUG in __bch2_btree_node_write syzbot
2024-11-25 6:52 ` [syzbot] syzbot
2024-09-28 2:13 [syzbot] [bcachefs?] kernel BUG in bch2_fs_btree_write_buffer_exit syzbot
2024-11-08 3:04 ` [syzbot] syzbot
2024-09-18 7:28 [syzbot] [bcachefs?] WARNING in bch2_journal_flush_seq_async syzbot
2024-11-28 22:50 ` [syzbot] syzbot
2024-08-27 2:12 [syzbot] [sound?] WARNING in snd_pcm_open syzbot
2024-09-06 10:33 ` [syzbot] syzbot
2024-07-30 1:14 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in journal_entry_dev_usage_to_text syzbot
2024-11-11 21:03 ` [syzbot] syzbot
2024-07-24 8:59 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in mgmt_remove_adv_monitor_sync syzbot
2024-12-05 1:58 ` [syzbot] syzbot
2024-12-23 22:19 ` [syzbot] syzbot
2024-07-17 13:39 [syzbot] [bcachefs?] general protection fault in bch2_checksum syzbot
2024-11-28 22:59 ` [syzbot] syzbot
2024-07-13 22:54 [syzbot] [bpf?] [trace?] possible deadlock in console_flush_all (3) syzbot
2025-06-19 20:48 ` [syzbot] syzbot
2024-07-10 20:55 [syzbot] [bcachefs?] kernel BUG in bch2_journal_noflush_seq syzbot
2024-11-28 22:12 ` [syzbot] syzbot
2024-06-14 12:16 [syzbot] [crypto?] [bcachefs?] BUG: unable to handle kernel paging request in crypto_skcipher_encrypt syzbot
2024-11-25 7:19 ` [syzbot] syzbot
[not found] <mailman.217.1706634262.2961.pvrusb2@isely.net>
2024-02-15 16:26 ` [syzbot] syzbot
2024-01-12 20:14 [syzbot] upstream build error (21) syzbot
2024-06-20 8:00 ` [syzbot] syzbot
2024-01-05 17:32 [syzbot] [net?] memory leak in ___neigh_create (2) syzbot
2024-09-05 11:54 ` [syzbot] syzbot
2023-11-16 11:09 [syzbot] [kernel?] inconsistent lock state in __lock_task_sighand syzbot
2024-09-06 10:37 ` [syzbot] syzbot
2023-11-15 9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
2023-11-16 2:33 ` [syzbot] syzbot
2023-11-16 3:29 ` [syzbot] syzbot
2023-10-16 7:38 [syzbot] [kernel?] KASAN: slab-use-after-free Read in reweight_entity syzbot
2024-09-06 10:38 ` [syzbot] syzbot
2023-06-05 3:53 [syzbot] [ext4?] WARNING: locking bug in ext4_move_extents syzbot
2024-07-03 7:48 ` [syzbot] syzbot
2022-10-17 7:43 [syzbot] possible deadlock in attr_data_get_block syzbot
2024-07-17 8:19 ` [syzbot] syzbot
2022-09-25 11:18 [syzbot] WARNING in __change_page_attr_set_clr syzbot
2024-09-06 10:39 ` [syzbot] syzbot
2022-07-12 12:03 [syzbot] inconsistent lock state in find_vmap_area syzbot
2024-09-06 10:36 ` [syzbot] syzbot
2022-02-10 19:17 [syzbot] general protection fault in blk_mq_free_rqs syzbot
2023-11-10 18:56 ` [syzbot] syzbot
2021-02-26 14:48 general protection fault in try_to_wake_up (2) syzbot
2024-07-25 16:29 ` [syzbot] syzbot
2021-02-01 10:07 BUG: Bad page state (8) syzbot
2024-10-28 14:11 ` [syzbot] syzbot
2020-11-21 1:55 INFO: task can't die in shrink_inactive_list (2) syzbot
2024-09-06 10:39 ` [syzbot] syzbot
2020-10-13 17:02 WARNING in drop_nlink (2) syzbot
2024-11-20 15:35 ` [syzbot] syzbot
2020-08-08 21:27 KASAN: use-after-free Read in __queue_work (3) syzbot
2024-09-06 10:40 ` [syzbot] syzbot
2020-08-04 15:46 KASAN: use-after-free Read in __sco_sock_close syzbot
2024-09-06 10:35 ` [syzbot] syzbot
2018-11-24 19:40 WARNING in csum_and_copy_to_iter syzbot
2023-11-24 10:30 ` [syzbot] 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