* 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ messages in thread
* Re: [syzbot] [pvrusb2?] KASAN: slab-use-after-free Read in pvr2_context_set_notify (2)
[not found] <mailman.217.1706634262.2961.pvrusb2@isely.net>
@ 2024-01-31 10:22 ` syzbot
2024-02-16 0:42 ` Hillf Danton
` (2 more replies)
2024-02-15 16:26 ` [syzbot] syzbot
1 sibling, 3 replies; 139+ messages in thread
From: syzbot @ 2024-01-31 10:22 UTC (permalink / raw)
To: isely, linux-kernel, linux-media, linux-usb, mchehab,
pvrusb2-owner, pvrusb2, syzkaller-bugs
syzbot has found a reproducer for the following issue on:
HEAD commit: f1a27f081c1f usb: typec: qcom-pmic-typec: allow different ..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=14800bdfe80000
kernel config: https://syzkaller.appspot.com/x/.config?x=986ce9258c6856ff
dashboard link: https://syzkaller.appspot.com/bug?extid=ce750e124675d4599449
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17c7cad3e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1429ed40180000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c77efcf770e8/disk-f1a27f08.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a827d6ba40bf/vmlinux-f1a27f08.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9d21d228bf73/bzImage-f1a27f08.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ce750e124675d4599449@syzkaller.appspotmail.com
pvrusb2: Device being rendered inoperable
==================================================================
BUG: KASAN: slab-use-after-free in pvr2_context_set_notify+0x2c4/0x310 drivers/media/usb/pvrusb2/pvrusb2-context.c:35
Read of size 4 at addr ffff888112202ad8 by task kworker/0:1/9
CPU: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.8.0-rc1-syzkaller-00046-gf1a27f081c1f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: usb_hub_wq hub_event
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:377 [inline]
print_report+0xc4/0x620 mm/kasan/report.c:488
kasan_report+0xda/0x110 mm/kasan/report.c:601
pvr2_context_set_notify+0x2c4/0x310 drivers/media/usb/pvrusb2/pvrusb2-context.c:35
pvr2_context_notify drivers/media/usb/pvrusb2/pvrusb2-context.c:95 [inline]
pvr2_context_disconnect+0x94/0xb0 drivers/media/usb/pvrusb2/pvrusb2-context.c:272
pvr_disconnect+0x80/0xf0 drivers/media/usb/pvrusb2/pvrusb2-main.c:79
usb_unbind_interface+0x1e5/0x960 drivers/usb/core/driver.c:461
device_remove drivers/base/dd.c:569 [inline]
device_remove+0x11f/0x170 drivers/base/dd.c:561
__device_release_driver drivers/base/dd.c:1272 [inline]
device_release_driver_internal+0x44a/0x610 drivers/base/dd.c:1295
bus_remove_device+0x22c/0x420 drivers/base/bus.c:574
device_del+0x39a/0xa50 drivers/base/core.c:3814
usb_disable_device+0x36c/0x7f0 drivers/usb/core/message.c:1416
usb_disconnect+0x2e1/0x910 drivers/usb/core/hub.c:2286
hub_port_connect drivers/usb/core/hub.c:5334 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5634 [inline]
port_event drivers/usb/core/hub.c:5794 [inline]
hub_event+0x1be0/0x4f40 drivers/usb/core/hub.c:5876
process_one_work+0x886/0x15d0 kernel/workqueue.c:2633
process_scheduled_works kernel/workqueue.c:2706 [inline]
worker_thread+0x8b9/0x1290 kernel/workqueue.c:2787
kthread+0x2c6/0x3a0 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
</TASK>
Allocated by task 9:
kasan_save_stack+0x33/0x50 mm/kasan/common.c:47
kasan_save_track+0x14/0x30 mm/kasan/common.c:68
poison_kmalloc_redzone mm/kasan/common.c:372 [inline]
__kasan_kmalloc+0x87/0x90 mm/kasan/common.c:389
kmalloc include/linux/slab.h:590 [inline]
kzalloc include/linux/slab.h:711 [inline]
pvr2_context_create+0x53/0x2a0 drivers/media/usb/pvrusb2/pvrusb2-context.c:207
pvr_probe+0x25/0xe0 drivers/media/usb/pvrusb2/pvrusb2-main.c:54
usb_probe_interface+0x307/0x9c0 drivers/usb/core/driver.c:399
call_driver_probe drivers/base/dd.c:579 [inline]
really_probe+0x234/0xc90 drivers/base/dd.c:658
__driver_probe_device+0x1de/0x4b0 drivers/base/dd.c:800
driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:830
__device_attach_driver+0x1d4/0x300 drivers/base/dd.c:958
bus_for_each_drv+0x157/0x1d0 drivers/base/bus.c:457
__device_attach+0x1e8/0x4b0 drivers/base/dd.c:1030
bus_probe_device+0x17c/0x1c0 drivers/base/bus.c:532
device_add+0x117e/0x1aa0 drivers/base/core.c:3625
usb_set_configuration+0x10cb/0x1c40 drivers/usb/core/message.c:2207
usb_generic_driver_probe+0xad/0x110 drivers/usb/core/generic.c:254
usb_probe_device+0xec/0x3e0 drivers/usb/core/driver.c:294
call_driver_probe drivers/base/dd.c:579 [inline]
really_probe+0x234/0xc90 drivers/base/dd.c:658
__driver_probe_device+0x1de/0x4b0 drivers/base/dd.c:800
driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:830
__device_attach_driver+0x1d4/0x300 drivers/base/dd.c:958
bus_for_each_drv+0x157/0x1d0 drivers/base/bus.c:457
__device_attach+0x1e8/0x4b0 drivers/base/dd.c:1030
bus_probe_device+0x17c/0x1c0 drivers/base/bus.c:532
device_add+0x117e/0x1aa0 drivers/base/core.c:3625
usb_new_device+0xd80/0x19f0 drivers/usb/core/hub.c:2625
hub_port_connect drivers/usb/core/hub.c:5494 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5634 [inline]
port_event drivers/usb/core/hub.c:5794 [inline]
hub_event+0x2e62/0x4f40 drivers/usb/core/hub.c:5876
process_one_work+0x886/0x15d0 kernel/workqueue.c:2633
process_scheduled_works kernel/workqueue.c:2706 [inline]
worker_thread+0x8b9/0x1290 kernel/workqueue.c:2787
kthread+0x2c6/0x3a0 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
Freed by task 901:
kasan_save_stack+0x33/0x50 mm/kasan/common.c:47
kasan_save_track+0x14/0x30 mm/kasan/common.c:68
kasan_save_free_info+0x3f/0x60 mm/kasan/generic.c:640
poison_slab_object mm/kasan/common.c:241 [inline]
__kasan_slab_free+0x106/0x1b0 mm/kasan/common.c:257
kasan_slab_free include/linux/kasan.h:184 [inline]
slab_free_hook mm/slub.c:2121 [inline]
slab_free mm/slub.c:4299 [inline]
kfree+0x105/0x340 mm/slub.c:4409
pvr2_context_check drivers/media/usb/pvrusb2/pvrusb2-context.c:137 [inline]
pvr2_context_thread_func+0x69d/0x960 drivers/media/usb/pvrusb2/pvrusb2-context.c:158
kthread+0x2c6/0x3a0 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
The buggy address belongs to the object at ffff888112202a00
which belongs to the cache kmalloc-256 of size 256
The buggy address is located 216 bytes inside of
freed 256-byte region [ffff888112202a00, ffff888112202b00)
The buggy address belongs to the physical page:
page:ffffea0004488080 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x112202
head:ffffea0004488080 order:1 entire_mapcount:0 nr_pages_mapped:0 pincount:0
anon flags: 0x200000000000840(slab|head|node=0|zone=2)
page_type: 0xffffffff()
raw: 0200000000000840 ffff888100041b40 ffffea0004498080 0000000000000005
raw: 0000000000000000 0000000000100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 1, migratetype Unmovable, gfp_mask 0xd20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 1, tgid 1 (swapper/0), ts 7680321640, free_ts 0
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x2d0/0x350 mm/page_alloc.c:1533
prep_new_page mm/page_alloc.c:1540 [inline]
get_page_from_freelist+0x139c/0x3470 mm/page_alloc.c:3311
__alloc_pages+0x228/0x2250 mm/page_alloc.c:4567
__alloc_pages_node include/linux/gfp.h:238 [inline]
alloc_pages_node include/linux/gfp.h:261 [inline]
alloc_slab_page mm/slub.c:2190 [inline]
allocate_slab mm/slub.c:2354 [inline]
new_slab+0xcc/0x3a0 mm/slub.c:2407
___slab_alloc+0x4b0/0x1860 mm/slub.c:3540
__slab_alloc.constprop.0+0x56/0xa0 mm/slub.c:3625
__slab_alloc_node mm/slub.c:3678 [inline]
slab_alloc_node mm/slub.c:3850 [inline]
__do_kmalloc_node mm/slub.c:3980 [inline]
__kmalloc_node_track_caller+0x171/0x420 mm/slub.c:4001
__do_krealloc mm/slab_common.c:1187 [inline]
krealloc+0x5d/0xf0 mm/slab_common.c:1220
add_sysfs_param+0xca/0x960 kernel/params.c:654
kernel_add_sysfs_param kernel/params.c:817 [inline]
param_sysfs_builtin kernel/params.c:856 [inline]
param_sysfs_builtin_init+0x2ca/0x450 kernel/params.c:990
do_one_initcall+0x11c/0x650 init/main.c:1236
do_initcall_level init/main.c:1298 [inline]
do_initcalls init/main.c:1314 [inline]
do_basic_setup init/main.c:1333 [inline]
kernel_init_freeable+0x682/0xc10 init/main.c:1551
kernel_init+0x1c/0x2a0 init/main.c:1441
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
page_owner free stack trace missing
Memory state around the buggy address:
ffff888112202980: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff888112202a00: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff888112202a80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff888112202b00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff888112202b80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================
---
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] 139+ messages in thread
* Re: [syzbot]
[not found] <mailman.217.1706634262.2961.pvrusb2@isely.net>
2024-01-31 10:22 ` [syzbot] [pvrusb2?] KASAN: slab-use-after-free Read in pvr2_context_set_notify (2) syzbot
@ 2024-02-15 16:26 ` syzbot
1 sibling, 0 replies; 139+ 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] 139+ messages in thread
* Re: [syzbot] [pvrusb2?] KASAN: slab-use-after-free Read in pvr2_context_set_notify (2)
2024-01-31 10:22 ` [syzbot] [pvrusb2?] KASAN: slab-use-after-free Read in pvr2_context_set_notify (2) syzbot
@ 2024-02-16 0:42 ` Hillf Danton
2024-02-16 4:58 ` syzbot
2024-02-16 3:03 ` Edward Adam Davis
2024-02-16 7:30 ` [PATCH usb] media/pvrusb2: fix uaf in pvr2_context_set_notify Edward Adam Davis
2 siblings, 1 reply; 139+ messages in thread
From: Hillf Danton @ 2024-02-16 0:42 UTC (permalink / raw)
To: syzbot; +Cc: linux-kernel, syzkaller-bugs
On Wed, 31 Jan 2024 02:22:39 -0800
> HEAD commit: f1a27f081c1f usb: typec: qcom-pmic-typec: allow different ..
> git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1429ed40180000
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
--- x/drivers/media/usb/pvrusb2/pvrusb2-context.c
+++ y/drivers/media/usb/pvrusb2/pvrusb2-context.c
@@ -267,9 +267,9 @@ static void pvr2_context_exit(struct pvr
void pvr2_context_disconnect(struct pvr2_context *mp)
{
pvr2_hdw_disconnect(mp->hdw);
- mp->disconnect_flag = !0;
if (!pvr2_context_shutok())
pvr2_context_notify(mp);
+ pvr2_context_destroy(mp);
}
--
^ permalink raw reply [flat|nested] 139+ messages in thread
* Re: [syzbot] [pvrusb2?] KASAN: slab-use-after-free Read in pvr2_context_set_notify (2)
2024-01-31 10:22 ` [syzbot] [pvrusb2?] KASAN: slab-use-after-free Read in pvr2_context_set_notify (2) syzbot
2024-02-16 0:42 ` Hillf Danton
@ 2024-02-16 3:03 ` Edward Adam Davis
2024-02-16 5:09 ` syzbot
2024-02-16 7:30 ` [PATCH usb] media/pvrusb2: fix uaf in pvr2_context_set_notify Edward Adam Davis
2 siblings, 1 reply; 139+ messages in thread
From: Edward Adam Davis @ 2024-02-16 3:03 UTC (permalink / raw)
To: syzbot+ce750e124675d4599449; +Cc: linux-kernel, syzkaller-bugs
please test uaf in pvr2_context_set_notify
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
diff --git a/drivers/media/usb/pvrusb2/pvrusb2-context.c b/drivers/media/usb/pvrusb2/pvrusb2-context.c
index 1764674de98b..e93bca93ce4c 100644
--- a/drivers/media/usb/pvrusb2/pvrusb2-context.c
+++ b/drivers/media/usb/pvrusb2/pvrusb2-context.c
@@ -267,9 +267,9 @@ static void pvr2_context_exit(struct pvr2_context *mp)
void pvr2_context_disconnect(struct pvr2_context *mp)
{
pvr2_hdw_disconnect(mp->hdw);
- mp->disconnect_flag = !0;
if (!pvr2_context_shutok())
pvr2_context_notify(mp);
+ mp->disconnect_flag = !0;
}
^ permalink raw reply related [flat|nested] 139+ messages in thread
* Re: [syzbot] [pvrusb2?] KASAN: slab-use-after-free Read in pvr2_context_set_notify (2)
2024-02-16 0:42 ` Hillf Danton
@ 2024-02-16 4:58 ` syzbot
0 siblings, 0 replies; 139+ messages in thread
From: syzbot @ 2024-02-16 4:58 UTC (permalink / raw)
To: hdanton, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KASAN: slab-use-after-free Read in pvr2_context_set_notify
pvrusb2: You might need to power cycle the pvrusb2 device in order to recover.
==================================================================
BUG: KASAN: slab-use-after-free in pvr2_context_set_notify+0x2ba/0x310 drivers/media/usb/pvrusb2/pvrusb2-context.c:48
Read of size 4 at addr ffff88810fb02ed8 by task pvrusb2-context/902
CPU: 0 PID: 902 Comm: pvrusb2-context Not tainted 6.8.0-rc4-syzkaller-00180-g4f5e5092fdbf-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:377 [inline]
print_report+0xc4/0x620 mm/kasan/report.c:488
kasan_report+0xda/0x110 mm/kasan/report.c:601
pvr2_context_set_notify+0x2ba/0x310 drivers/media/usb/pvrusb2/pvrusb2-context.c:48
pvr2_context_thread_func+0x10d/0x960 drivers/media/usb/pvrusb2/pvrusb2-context.c:157
kthread+0x2c6/0x3a0 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
</TASK>
Allocated by task 724:
kasan_save_stack+0x33/0x50 mm/kasan/common.c:47
kasan_save_track+0x14/0x30 mm/kasan/common.c:68
poison_kmalloc_redzone mm/kasan/common.c:372 [inline]
__kasan_kmalloc+0x87/0x90 mm/kasan/common.c:389
kmalloc include/linux/slab.h:590 [inline]
kzalloc include/linux/slab.h:711 [inline]
pvr2_context_create+0x53/0x2a0 drivers/media/usb/pvrusb2/pvrusb2-context.c:207
pvr_probe+0x25/0xe0 drivers/media/usb/pvrusb2/pvrusb2-main.c:54
usb_probe_interface+0x307/0x930 drivers/usb/core/driver.c:399
call_driver_probe drivers/base/dd.c:579 [inline]
really_probe+0x234/0xc90 drivers/base/dd.c:658
__driver_probe_device+0x1de/0x4b0 drivers/base/dd.c:800
driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:830
__device_attach_driver+0x1d4/0x300 drivers/base/dd.c:958
bus_for_each_drv+0x157/0x1d0 drivers/base/bus.c:457
__device_attach+0x1e8/0x4b0 drivers/base/dd.c:1030
bus_probe_device+0x17c/0x1c0 drivers/base/bus.c:532
device_add+0x117e/0x1aa0 drivers/base/core.c:3625
usb_set_configuration+0x10cb/0x1c40 drivers/usb/core/message.c:2207
usb_generic_driver_probe+0xad/0x110 drivers/usb/core/generic.c:254
usb_probe_device+0xec/0x350 drivers/usb/core/driver.c:294
call_driver_probe drivers/base/dd.c:579 [inline]
really_probe+0x234/0xc90 drivers/base/dd.c:658
__driver_probe_device+0x1de/0x4b0 drivers/base/dd.c:800
driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:830
__device_attach_driver+0x1d4/0x300 drivers/base/dd.c:958
bus_for_each_drv+0x157/0x1d0 drivers/base/bus.c:457
__device_attach+0x1e8/0x4b0 drivers/base/dd.c:1030
bus_probe_device+0x17c/0x1c0 drivers/base/bus.c:532
device_add+0x117e/0x1aa0 drivers/base/core.c:3625
usb_new_device+0xd90/0x1a10 drivers/usb/core/hub.c:2614
hub_port_connect drivers/usb/core/hub.c:5483 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5623 [inline]
port_event drivers/usb/core/hub.c:5783 [inline]
hub_event+0x2e62/0x4f40 drivers/usb/core/hub.c:5865
process_one_work+0x886/0x15d0 kernel/workqueue.c:2633
process_scheduled_works kernel/workqueue.c:2706 [inline]
worker_thread+0x8b9/0x1290 kernel/workqueue.c:2787
kthread+0x2c6/0x3a0 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
Freed by task 724:
kasan_save_stack+0x33/0x50 mm/kasan/common.c:47
kasan_save_track+0x14/0x30 mm/kasan/common.c:68
kasan_save_free_info+0x3f/0x60 mm/kasan/generic.c:640
poison_slab_object mm/kasan/common.c:241 [inline]
__kasan_slab_free+0x106/0x1b0 mm/kasan/common.c:257
kasan_slab_free include/linux/kasan.h:184 [inline]
slab_free_hook mm/slub.c:2121 [inline]
slab_free mm/slub.c:4299 [inline]
kfree+0x105/0x340 mm/slub.c:4409
pvr_disconnect+0x80/0xf0 drivers/media/usb/pvrusb2/pvrusb2-main.c:79
usb_unbind_interface+0x1dd/0x8d0 drivers/usb/core/driver.c:461
device_remove drivers/base/dd.c:569 [inline]
device_remove+0x11f/0x170 drivers/base/dd.c:561
__device_release_driver drivers/base/dd.c:1272 [inline]
device_release_driver_internal+0x44a/0x610 drivers/base/dd.c:1295
bus_remove_device+0x22c/0x420 drivers/base/bus.c:574
device_del+0x39a/0xa50 drivers/base/core.c:3814
usb_disable_device+0x36c/0x7f0 drivers/usb/core/message.c:1416
usb_disconnect+0x2e1/0x910 drivers/usb/core/hub.c:2267
hub_port_connect drivers/usb/core/hub.c:5323 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5623 [inline]
port_event drivers/usb/core/hub.c:5783 [inline]
hub_event+0x1be0/0x4f40 drivers/usb/core/hub.c:5865
process_one_work+0x886/0x15d0 kernel/workqueue.c:2633
process_scheduled_works kernel/workqueue.c:2706 [inline]
worker_thread+0x8b9/0x1290 kernel/workqueue.c:2787
kthread+0x2c6/0x3a0 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
The buggy address belongs to the object at ffff88810fb02e00
which belongs to the cache kmalloc-256 of size 256
The buggy address is located 216 bytes inside of
freed 256-byte region [ffff88810fb02e00, ffff88810fb02f00)
The buggy address belongs to the physical page:
page:ffffea00043ec080 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10fb02
head:ffffea00043ec080 order:1 entire_mapcount:0 nr_pages_mapped:0 pincount:0
flags: 0x200000000000840(slab|head|node=0|zone=2)
page_type: 0xffffffff()
raw: 0200000000000840 ffff888100041b40 ffffea00041ef600 0000000000000002
raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 1, migratetype Unmovable, gfp_mask 0x1d20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL), pid 5358, tgid 5358 (kworker/1:4), ts 131458586273, free_ts 131438325014
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x2d0/0x350 mm/page_alloc.c:1533
prep_new_page mm/page_alloc.c:1540 [inline]
get_page_from_freelist+0x139c/0x3470 mm/page_alloc.c:3311
__alloc_pages+0x228/0x2250 mm/page_alloc.c:4567
__alloc_pages_node include/linux/gfp.h:238 [inline]
alloc_pages_node include/linux/gfp.h:261 [inline]
alloc_slab_page mm/slub.c:2190 [inline]
allocate_slab mm/slub.c:2354 [inline]
new_slab+0xcc/0x3a0 mm/slub.c:2407
___slab_alloc+0x4b0/0x1860 mm/slub.c:3540
__slab_alloc.constprop.0+0x56/0xa0 mm/slub.c:3625
__slab_alloc_node mm/slub.c:3678 [inline]
slab_alloc_node mm/slub.c:3850 [inline]
kmalloc_trace+0x2ce/0x300 mm/slub.c:4007
kmalloc include/linux/slab.h:590 [inline]
kzalloc include/linux/slab.h:711 [inline]
pvr2_context_create+0x53/0x2a0 drivers/media/usb/pvrusb2/pvrusb2-context.c:207
pvr_probe+0x25/0xe0 drivers/media/usb/pvrusb2/pvrusb2-main.c:54
usb_probe_interface+0x307/0x930 drivers/usb/core/driver.c:399
call_driver_probe drivers/base/dd.c:579 [inline]
really_probe+0x234/0xc90 drivers/base/dd.c:658
__driver_probe_device+0x1de/0x4b0 drivers/base/dd.c:800
driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:830
__device_attach_driver+0x1d4/0x300 drivers/base/dd.c:958
bus_for_each_drv+0x157/0x1d0 drivers/base/bus.c:457
__device_attach+0x1e8/0x4b0 drivers/base/dd.c:1030
page last free pid 5341 tgid 5341 stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1140 [inline]
free_unref_page_prepare+0x504/0xae0 mm/page_alloc.c:2346
free_unref_page+0x33/0x2d0 mm/page_alloc.c:2486
qlink_free mm/kasan/quarantine.c:160 [inline]
qlist_free_all+0x58/0x150 mm/kasan/quarantine.c:176
kasan_quarantine_reduce+0x18e/0x1d0 mm/kasan/quarantine.c:283
__kasan_slab_alloc+0x4a/0x70 mm/kasan/common.c:324
kasan_slab_alloc include/linux/kasan.h:201 [inline]
slab_post_alloc_hook mm/slub.c:3813 [inline]
slab_alloc_node mm/slub.c:3860 [inline]
kmem_cache_alloc+0x131/0x2e0 mm/slub.c:3867
getname_flags.part.0+0x50/0x4e0 fs/namei.c:140
getname_flags+0x9c/0xf0 include/linux/audit.h:322
vfs_fstatat+0x9a/0x140 fs/stat.c:303
__do_sys_newfstatat+0x98/0x110 fs/stat.c:468
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xd3/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b
Memory state around the buggy address:
ffff88810fb02d80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff88810fb02e00: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88810fb02e80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff88810fb02f00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff88810fb02f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================
Tested on:
commit: 4f5e5092 Merge tag 'net-6.8-rc5' of git://git.kernel.o..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=17133c1c180000
kernel config: https://syzkaller.appspot.com/x/.config?x=4f5e432f25b85a97
dashboard link: https://syzkaller.appspot.com/bug?extid=ce750e124675d4599449
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=12c58494180000
^ permalink raw reply [flat|nested] 139+ messages in thread
* Re: [syzbot] [pvrusb2?] KASAN: slab-use-after-free Read in pvr2_context_set_notify (2)
2024-02-16 3:03 ` Edward Adam Davis
@ 2024-02-16 5:09 ` syzbot
0 siblings, 0 replies; 139+ messages in thread
From: syzbot @ 2024-02-16 5:09 UTC (permalink / raw)
To: eadavis, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+ce750e124675d4599449@syzkaller.appspotmail.com
Tested on:
commit: 88bae831 usb: typec: ucsi: Add qcm6490-pmic-glink as n..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=16675a78180000
kernel config: https://syzkaller.appspot.com/x/.config?x=28a3704ea90ef255
dashboard link: https://syzkaller.appspot.com/bug?extid=ce750e124675d4599449
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=15e33c1c180000
Note: testing is done by a robot and is best-effort only.
^ permalink raw reply [flat|nested] 139+ messages in thread
* [PATCH usb] media/pvrusb2: fix uaf in pvr2_context_set_notify
2024-01-31 10:22 ` [syzbot] [pvrusb2?] KASAN: slab-use-after-free Read in pvr2_context_set_notify (2) syzbot
2024-02-16 0:42 ` Hillf Danton
2024-02-16 3:03 ` Edward Adam Davis
@ 2024-02-16 7:30 ` Edward Adam Davis
2024-02-17 7:41 ` Greg KH
2 siblings, 1 reply; 139+ messages in thread
From: Edward Adam Davis @ 2024-02-16 7:30 UTC (permalink / raw)
To: syzbot+ce750e124675d4599449
Cc: isely, linux-kernel, linux-media, linux-usb, mchehab,
pvrusb2-owner, pvrusb2, syzkaller-bugs
[Syzbot reported]
BUG: KASAN: slab-use-after-free in pvr2_context_set_notify+0x2c4/0x310 drivers/media/usb/pvrusb2/pvrusb2-context.c:35
Read of size 4 at addr ffff888113aeb0d8 by task kworker/1:1/26
CPU: 1 PID: 26 Comm: kworker/1:1 Not tainted 6.8.0-rc1-syzkaller-00046-gf1a27f081c1f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: usb_hub_wq hub_event
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:377 [inline]
print_report+0xc4/0x620 mm/kasan/report.c:488
kasan_report+0xda/0x110 mm/kasan/report.c:601
pvr2_context_set_notify+0x2c4/0x310 drivers/media/usb/pvrusb2/pvrusb2-context.c:35
pvr2_context_notify drivers/media/usb/pvrusb2/pvrusb2-context.c:95 [inline]
pvr2_context_disconnect+0x94/0xb0 drivers/media/usb/pvrusb2/pvrusb2-context.c:272
Freed by task 906:
kasan_save_stack+0x33/0x50 mm/kasan/common.c:47
kasan_save_track+0x14/0x30 mm/kasan/common.c:68
kasan_save_free_info+0x3f/0x60 mm/kasan/generic.c:640
poison_slab_object mm/kasan/common.c:241 [inline]
__kasan_slab_free+0x106/0x1b0 mm/kasan/common.c:257
kasan_slab_free include/linux/kasan.h:184 [inline]
slab_free_hook mm/slub.c:2121 [inline]
slab_free mm/slub.c:4299 [inline]
kfree+0x105/0x340 mm/slub.c:4409
pvr2_context_check drivers/media/usb/pvrusb2/pvrusb2-context.c:137 [inline]
pvr2_context_thread_func+0x69d/0x960 drivers/media/usb/pvrusb2/pvrusb2-context.c:158
[Analyze]
Task A set disconnect_flag = !0, which resulted in Task B's condition being met
and releasing mp, leading to this issue.
[Fix]
Place the disconnect_flag assignment operation after all code in pvr2_context_disconnect()
to avoid this issue.
Reported-and-tested-by: syzbot+ce750e124675d4599449@syzkaller.appspotmail.com
Signed-off-by: Edward Adam Davis <eadavis@qq.com>
---
drivers/media/usb/pvrusb2/pvrusb2-context.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/usb/pvrusb2/pvrusb2-context.c b/drivers/media/usb/pvrusb2/pvrusb2-context.c
index 1764674de98b..e93bca93ce4c 100644
--- a/drivers/media/usb/pvrusb2/pvrusb2-context.c
+++ b/drivers/media/usb/pvrusb2/pvrusb2-context.c
@@ -267,9 +267,9 @@ static void pvr2_context_exit(struct pvr2_context *mp)
void pvr2_context_disconnect(struct pvr2_context *mp)
{
pvr2_hdw_disconnect(mp->hdw);
- mp->disconnect_flag = !0;
if (!pvr2_context_shutok())
pvr2_context_notify(mp);
+ mp->disconnect_flag = !0;
}
--
2.43.0
^ permalink raw reply related [flat|nested] 139+ messages in thread
* Re: [PATCH usb] media/pvrusb2: fix uaf in pvr2_context_set_notify
2024-02-16 7:30 ` [PATCH usb] media/pvrusb2: fix uaf in pvr2_context_set_notify Edward Adam Davis
@ 2024-02-17 7:41 ` Greg KH
2024-02-18 6:22 ` Edward Adam Davis
2024-03-02 2:08 ` [PATCH usb V2] " Edward Adam Davis
0 siblings, 2 replies; 139+ messages in thread
From: Greg KH @ 2024-02-17 7:41 UTC (permalink / raw)
To: Edward Adam Davis
Cc: syzbot+ce750e124675d4599449, isely, linux-kernel, linux-media,
linux-usb, mchehab, pvrusb2-owner, pvrusb2, syzkaller-bugs
On Fri, Feb 16, 2024 at 03:30:47PM +0800, Edward Adam Davis wrote:
> [Syzbot reported]
> BUG: KASAN: slab-use-after-free in pvr2_context_set_notify+0x2c4/0x310 drivers/media/usb/pvrusb2/pvrusb2-context.c:35
> Read of size 4 at addr ffff888113aeb0d8 by task kworker/1:1/26
>
> CPU: 1 PID: 26 Comm: kworker/1:1 Not tainted 6.8.0-rc1-syzkaller-00046-gf1a27f081c1f #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
> Workqueue: usb_hub_wq hub_event
> Call Trace:
> <TASK>
> __dump_stack lib/dump_stack.c:88 [inline]
> dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
> print_address_description mm/kasan/report.c:377 [inline]
> print_report+0xc4/0x620 mm/kasan/report.c:488
> kasan_report+0xda/0x110 mm/kasan/report.c:601
> pvr2_context_set_notify+0x2c4/0x310 drivers/media/usb/pvrusb2/pvrusb2-context.c:35
> pvr2_context_notify drivers/media/usb/pvrusb2/pvrusb2-context.c:95 [inline]
> pvr2_context_disconnect+0x94/0xb0 drivers/media/usb/pvrusb2/pvrusb2-context.c:272
>
> Freed by task 906:
> kasan_save_stack+0x33/0x50 mm/kasan/common.c:47
> kasan_save_track+0x14/0x30 mm/kasan/common.c:68
> kasan_save_free_info+0x3f/0x60 mm/kasan/generic.c:640
> poison_slab_object mm/kasan/common.c:241 [inline]
> __kasan_slab_free+0x106/0x1b0 mm/kasan/common.c:257
> kasan_slab_free include/linux/kasan.h:184 [inline]
> slab_free_hook mm/slub.c:2121 [inline]
> slab_free mm/slub.c:4299 [inline]
> kfree+0x105/0x340 mm/slub.c:4409
> pvr2_context_check drivers/media/usb/pvrusb2/pvrusb2-context.c:137 [inline]
> pvr2_context_thread_func+0x69d/0x960 drivers/media/usb/pvrusb2/pvrusb2-context.c:158
>
> [Analyze]
> Task A set disconnect_flag = !0, which resulted in Task B's condition being met
> and releasing mp, leading to this issue.
>
> [Fix]
> Place the disconnect_flag assignment operation after all code in pvr2_context_disconnect()
> to avoid this issue.
>
> Reported-and-tested-by: syzbot+ce750e124675d4599449@syzkaller.appspotmail.com
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
What commit id does this fix?
And should it be cc: stable as well?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 139+ messages in thread
* Re: [PATCH usb] media/pvrusb2: fix uaf in pvr2_context_set_notify
2024-02-17 7:41 ` Greg KH
@ 2024-02-18 6:22 ` Edward Adam Davis
2024-03-02 2:08 ` [PATCH usb V2] " Edward Adam Davis
1 sibling, 0 replies; 139+ messages in thread
From: Edward Adam Davis @ 2024-02-18 6:22 UTC (permalink / raw)
To: greg
Cc: eadavis, isely, linux-kernel, linux-media, linux-usb, mchehab,
pvrusb2-owner, pvrusb2, syzbot+ce750e124675d4599449,
syzkaller-bugs
On Sat, 17 Feb 2024 08:41:33 +0100, Greg KH wrote:
> On Fri, Feb 16, 2024 at 03:30:47PM +0800, Edward Adam Davis wrote:
> > [Syzbot reported]
> > BUG: KASAN: slab-use-after-free in pvr2_context_set_notify+0x2c4/0x310 drivers/media/usb/pvrusb2/pvrusb2-context.c:35
> > Read of size 4 at addr ffff888113aeb0d8 by task kworker/1:1/26
> >
> > CPU: 1 PID: 26 Comm: kworker/1:1 Not tainted 6.8.0-rc1-syzkaller-00046-gf1a27f081c1f #0
> > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
> > Workqueue: usb_hub_wq hub_event
> > Call Trace:
> > <TASK>
> > __dump_stack lib/dump_stack.c:88 [inline]
> > dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
> > print_address_description mm/kasan/report.c:377 [inline]
> > print_report+0xc4/0x620 mm/kasan/report.c:488
> > kasan_report+0xda/0x110 mm/kasan/report.c:601
> > pvr2_context_set_notify+0x2c4/0x310 drivers/media/usb/pvrusb2/pvrusb2-context.c:35
> > pvr2_context_notify drivers/media/usb/pvrusb2/pvrusb2-context.c:95 [inline]
> > pvr2_context_disconnect+0x94/0xb0 drivers/media/usb/pvrusb2/pvrusb2-context.c:272
> >
> > Freed by task 906:
> > kasan_save_stack+0x33/0x50 mm/kasan/common.c:47
> > kasan_save_track+0x14/0x30 mm/kasan/common.c:68
> > kasan_save_free_info+0x3f/0x60 mm/kasan/generic.c:640
> > poison_slab_object mm/kasan/common.c:241 [inline]
> > __kasan_slab_free+0x106/0x1b0 mm/kasan/common.c:257
> > kasan_slab_free include/linux/kasan.h:184 [inline]
> > slab_free_hook mm/slub.c:2121 [inline]
> > slab_free mm/slub.c:4299 [inline]
> > kfree+0x105/0x340 mm/slub.c:4409
> > pvr2_context_check drivers/media/usb/pvrusb2/pvrusb2-context.c:137 [inline]
> > pvr2_context_thread_func+0x69d/0x960 drivers/media/usb/pvrusb2/pvrusb2-context.c:158
> >
> > [Analyze]
> > Task A set disconnect_flag = !0, which resulted in Task B's condition being met
> > and releasing mp, leading to this issue.
> >
> > [Fix]
> > Place the disconnect_flag assignment operation after all code in pvr2_context_disconnect()
> > to avoid this issue.
> >
> > Reported-and-tested-by: syzbot+ce750e124675d4599449@syzkaller.appspotmail.com
> > Signed-off-by: Edward Adam Davis <eadavis@qq.com>
>
> What commit id does this fix?
e5be15c63804 ("V4L/DVB (7711): pvrusb2: Fix race on module unload")
>
> And should it be cc: stable as well?
I checked the stable git tree and it introduced e5be15c63804. I think we need to
cc stable.
thanks,
edward
^ permalink raw reply [flat|nested] 139+ messages in thread
* [PATCH usb V2] media/pvrusb2: fix uaf in pvr2_context_set_notify
2024-02-17 7:41 ` Greg KH
2024-02-18 6:22 ` Edward Adam Davis
@ 2024-03-02 2:08 ` Edward Adam Davis
1 sibling, 0 replies; 139+ messages in thread
From: Edward Adam Davis @ 2024-03-02 2:08 UTC (permalink / raw)
To: greg
Cc: eadavis, isely, linux-kernel, linux-media, linux-usb, mchehab,
pvrusb2-owner, pvrusb2, syzbot+ce750e124675d4599449,
syzkaller-bugs
[Syzbot reported]
BUG: KASAN: slab-use-after-free in pvr2_context_set_notify+0x2c4/0x310 drivers/media/usb/pvrusb2/pvrusb2-context.c:35
Read of size 4 at addr ffff888113aeb0d8 by task kworker/1:1/26
CPU: 1 PID: 26 Comm: kworker/1:1 Not tainted 6.8.0-rc1-syzkaller-00046-gf1a27f081c1f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: usb_hub_wq hub_event
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:377 [inline]
print_report+0xc4/0x620 mm/kasan/report.c:488
kasan_report+0xda/0x110 mm/kasan/report.c:601
pvr2_context_set_notify+0x2c4/0x310 drivers/media/usb/pvrusb2/pvrusb2-context.c:35
pvr2_context_notify drivers/media/usb/pvrusb2/pvrusb2-context.c:95 [inline]
pvr2_context_disconnect+0x94/0xb0 drivers/media/usb/pvrusb2/pvrusb2-context.c:272
Freed by task 906:
kasan_save_stack+0x33/0x50 mm/kasan/common.c:47
kasan_save_track+0x14/0x30 mm/kasan/common.c:68
kasan_save_free_info+0x3f/0x60 mm/kasan/generic.c:640
poison_slab_object mm/kasan/common.c:241 [inline]
__kasan_slab_free+0x106/0x1b0 mm/kasan/common.c:257
kasan_slab_free include/linux/kasan.h:184 [inline]
slab_free_hook mm/slub.c:2121 [inline]
slab_free mm/slub.c:4299 [inline]
kfree+0x105/0x340 mm/slub.c:4409
pvr2_context_check drivers/media/usb/pvrusb2/pvrusb2-context.c:137 [inline]
pvr2_context_thread_func+0x69d/0x960 drivers/media/usb/pvrusb2/pvrusb2-context.c:158
[Analyze]
Task A set disconnect_flag = !0, which resulted in Task B's condition being met
and releasing mp, leading to this issue.
[Fix]
Place the disconnect_flag assignment operation after all code in pvr2_context_disconnect()
to avoid this issue.
Reported-and-tested-by: syzbot+ce750e124675d4599449@syzkaller.appspotmail.com
Fixes: e5be15c63804 ("V4L/DVB (7711): pvrusb2: Fix race on module unload")
cc: stable@vger.kernel.org
Signed-off-by: Edward Adam Davis <eadavis@qq.com>
---
drivers/media/usb/pvrusb2/pvrusb2-context.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/usb/pvrusb2/pvrusb2-context.c b/drivers/media/usb/pvrusb2/pvrusb2-context.c
index 1764674de98b..e93bca93ce4c 100644
--- a/drivers/media/usb/pvrusb2/pvrusb2-context.c
+++ b/drivers/media/usb/pvrusb2/pvrusb2-context.c
@@ -267,9 +267,9 @@ static void pvr2_context_exit(struct pvr2_context *mp)
void pvr2_context_disconnect(struct pvr2_context *mp)
{
pvr2_hdw_disconnect(mp->hdw);
- mp->disconnect_flag = !0;
if (!pvr2_context_shutok())
pvr2_context_notify(mp);
+ mp->disconnect_flag = !0;
}
--
2.43.0
^ permalink raw reply related [flat|nested] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ messages in thread
* Re: [syzbot]
2022-12-21 8:15 [syzbot] possible deadlock in page_cache_ra_unbounded syzbot
@ 2025-01-08 16:11 ` syzbot
0 siblings, 0 replies; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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 related [flat|nested] 139+ messages in thread
* Re: [syzbot]
2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
@ 2025-04-07 14:17 ` syzbot
0 siblings, 0 replies; 139+ 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] 139+ 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; 139+ 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 related [flat|nested] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ 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; 139+ 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] 139+ messages in thread
end of thread, other threads:[~2025-06-19 21:00 UTC | newest]
Thread overview: 139+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <mailman.217.1706634262.2961.pvrusb2@isely.net>
2024-01-31 10:22 ` [syzbot] [pvrusb2?] KASAN: slab-use-after-free Read in pvr2_context_set_notify (2) syzbot
2024-02-16 0:42 ` Hillf Danton
2024-02-16 4:58 ` syzbot
2024-02-16 3:03 ` Edward Adam Davis
2024-02-16 5:09 ` syzbot
2024-02-16 7:30 ` [PATCH usb] media/pvrusb2: fix uaf in pvr2_context_set_notify Edward Adam Davis
2024-02-17 7:41 ` Greg KH
2024-02-18 6:22 ` Edward Adam Davis
2024-03-02 2:08 ` [PATCH usb V2] " Edward Adam Davis
2024-02-15 16:26 ` [syzbot] syzbot
2025-06-12 7:52 [syzbot] [bcachefs?] WARNING in __init_work (2) syzbot
2025-06-19 20:54 ` [syzbot] syzbot
-- strict thread matches above, loose matches on Subject: below --
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?] kernel BUG in bch2_btree_pos_to_text (2) syzbot
2024-11-25 3:59 ` [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 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
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-12-21 8:15 [syzbot] possible deadlock in page_cache_ra_unbounded syzbot
2025-01-08 16:11 ` [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;
as well as URLs for NNTP newsgroup(s).