* [syzbot] [usb?] general protection fault in status_show
@ 2025-01-17 6:14 syzbot
2025-01-17 15:41 ` [syzbot] syzbot
` (4 more replies)
0 siblings, 5 replies; 138+ messages in thread
From: syzbot @ 2025-01-17 6:14 UTC (permalink / raw)
To: gregkh, i, linux-kernel, linux-usb, shuah, syzkaller-bugs,
valentina.manea.m
Hello,
syzbot found the following issue on:
HEAD commit: be548645527a Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=105adbc4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ad08f7f48e13abcd
dashboard link: https://syzkaller.appspot.com/bug?extid=83976e47ec1ef91e66f1
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=179bbef8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12d51cb0580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/68edb33a6611/disk-be548645.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9c748ff58068/vmlinux-be548645.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6ae2859fc0e3/bzImage-be548645.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+83976e47ec1ef91e66f1@syzkaller.appspotmail.com
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000081: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000408-0x000000000000040f]
CPU: 0 UID: 0 PID: 5830 Comm: syz-executor351 Not tainted 6.13.0-rc6-syzkaller-00290-gbe548645527a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:status_show_vhci drivers/usb/usbip/vhci_sysfs.c:80 [inline]
RIP: 0010:status_show+0x306/0x5a0 drivers/usb/usbip/vhci_sysfs.c:160
Code: 03 80 3c 02 00 0f 85 9c 02 00 00 48 8b 9b 88 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d bb 08 04 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 7d 02 00 00 4c 8b ab 08 04 00 00 c1 e5 04 41 bf
RSP: 0018:ffffc90003cbfad8 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff87534bb9
RDX: 0000000000000081 RSI: ffffffff87534d75 RDI: 0000000000000408
RBP: 000000000000000f R08: 0000000000000005 R09: 0000000000000000
R10: 000000000000000f R11: 64666b636f732020 R12: ffffc90003cbfb28
R13: ffff888034b8c02d R14: ffffffff87534ab0 R15: ffff888034b8c000
FS: 0000555582a4a380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000000 CR3: 0000000035336000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
dev_attr_show+0x53/0xe0 drivers/base/core.c:2423
sysfs_kf_seq_show+0x223/0x3e0 fs/sysfs/file.c:59
seq_read_iter+0x4f4/0x12b0 fs/seq_file.c:230
kernfs_fop_read_iter+0x414/0x580 fs/kernfs/file.c:279
new_sync_read fs/read_write.c:484 [inline]
vfs_read+0x87f/0xbe0 fs/read_write.c:565
ksys_read+0x12b/0x250 fs/read_write.c:708
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f5c749f72e9
Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fffd7fbd308 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007fffd7fbd4d8 RCX: 00007f5c749f72e9
RDX: 0000000000000062 RSI: 0000000020001080 RDI: 0000000000000003
RBP: 00007f5c74a6a610 R08: 0000000000000000 R09: 00007fffd7fbd4d8
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fffd7fbd4c8 R14: 0000000000000001 R15: 0000000000000001
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:status_show_vhci drivers/usb/usbip/vhci_sysfs.c:80 [inline]
RIP: 0010:status_show+0x306/0x5a0 drivers/usb/usbip/vhci_sysfs.c:160
Code: 03 80 3c 02 00 0f 85 9c 02 00 00 48 8b 9b 88 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8d bb 08 04 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 7d 02 00 00 4c 8b ab 08 04 00 00 c1 e5 04 41 bf
RSP: 0018:ffffc90003cbfad8 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff87534bb9
RDX: 0000000000000081 RSI: ffffffff87534d75 RDI: 0000000000000408
RBP: 000000000000000f R08: 0000000000000005 R09: 0000000000000000
R10: 000000000000000f R11: 64666b636f732020 R12: ffffc90003cbfb28
R13: ffff888034b8c02d R14: ffffffff87534ab0 R15: ffff888034b8c000
FS: 0000555582a4a380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000000 CR3: 0000000035336000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 03 80 3c 02 00 0f add 0xf00023c(%rax),%eax
6: 85 9c 02 00 00 48 8b test %ebx,-0x74b80000(%rdx,%rax,1)
d: 9b fwait
e: 88 00 mov %al,(%rax)
10: 00 00 add %al,(%rax)
12: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
19: fc ff df
1c: 48 8d bb 08 04 00 00 lea 0x408(%rbx),%rdi
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 7d 02 00 00 jne 0x2b1
34: 4c 8b ab 08 04 00 00 mov 0x408(%rbx),%r13
3b: c1 e5 04 shl $0x4,%ebp
3e: 41 rex.B
3f: bf .byte 0xbf
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
^ permalink raw reply [flat|nested] 138+ 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
2025-01-22 22:19 ` [syzbot] Re: [syzbot] [usb?] general protection fault in status_show syzbot
` (3 subsequent siblings)
4 siblings, 0 replies; 138+ 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] 138+ messages in thread
* Re: [syzbot] Re: [syzbot] [usb?] general protection fault in status_show
2025-01-17 6:14 [syzbot] [usb?] general protection fault in status_show syzbot
2025-01-17 15:41 ` [syzbot] syzbot
@ 2025-01-22 22:19 ` syzbot
2025-01-23 11:31 ` Hillf Danton
` (2 subsequent siblings)
4 siblings, 0 replies; 138+ messages in thread
From: syzbot @ 2025-01-22 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: Re: [syzbot] [usb?] general protection fault in status_show
Author: skhan@linuxfoundation.org
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux.git usbip_test
^ permalink raw reply [flat|nested] 138+ messages in thread
* Re: [syzbot] [usb?] general protection fault in status_show
2025-01-17 6:14 [syzbot] [usb?] general protection fault in status_show syzbot
2025-01-17 15:41 ` [syzbot] syzbot
2025-01-22 22:19 ` [syzbot] Re: [syzbot] [usb?] general protection fault in status_show syzbot
@ 2025-01-23 11:31 ` Hillf Danton
2025-01-23 11:45 ` syzbot
2025-01-24 11:17 ` Hillf Danton
2025-01-25 10:23 ` Hillf Danton
4 siblings, 1 reply; 138+ messages in thread
From: Hillf Danton @ 2025-01-23 11:31 UTC (permalink / raw)
To: syzbot; +Cc: linux-kernel, syzkaller-bugs
On Thu, 16 Jan 2025 22:14:23 -0800
> syzbot found the following issue on:
>
> HEAD commit: be548645527a Merge tag 'for-linus' of git://git.kernel.org..
> git tree: upstream
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12d51cb0580000
#syz test
--- x/drivers/usb/usbip/vhci_sysfs.c
+++ y/drivers/usb/usbip/vhci_sysfs.c
@@ -76,6 +76,8 @@ static ssize_t status_show_vhci(int pdev
}
hcd = platform_get_drvdata(pdev);
+ if (!usb_hcd_is_primary_hcd(hcd))
+ return 0;
vhci_hcd = hcd_to_vhci_hcd(hcd);
vhci = vhci_hcd->vhci;
--
^ permalink raw reply [flat|nested] 138+ messages in thread
* Re: [syzbot] [usb?] general protection fault in status_show
2025-01-23 11:31 ` Hillf Danton
@ 2025-01-23 11:45 ` syzbot
0 siblings, 0 replies; 138+ messages in thread
From: syzbot @ 2025-01-23 11:45 UTC (permalink / raw)
To: hdanton, linux-kernel, syzkaller-bugs
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
slave bond_slave_0): Enslaving as an active interface with an up link
[ 77.012704][ T5924] bond0: (slave bond_slave_1): Enslaving as an active interface with an up link
[ 77.039135][ T5924] team0: Port device team_slave_0 added
[ 77.046395][ T5924] team0: Port device team_slave_1 added
[ 77.067282][ T5924] batman_adv: batadv0: Adding interface: batadv_slave_0
[ 77.074614][ T5924] batman_adv: batadv0: The MTU of interface batadv_slave_0 is too small (1500) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1560 would solve the problem.
[ 77.101175][ T5924] batman_adv: batadv0: Not using interface batadv_slave_0 (retrying later): interface not active
[ 77.114964][ T5924] batman_adv: batadv0: Adding interface: batadv_slave_1
[ 77.122115][ T5924] batman_adv: batadv0: The MTU of interface batadv_slave_1 is too small (1500) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1560 would solve the problem.
[ 77.148711][ T5924] batman_adv: batadv0: Not using interface batadv_slave_1 (retrying later): interface not active
[ 77.184083][ T5924] hsr_slave_0: entered promiscuous mode
[ 77.190764][ T5924] hsr_slave_1: entered promiscuous mode
[ 77.196800][ T5924] debugfs: Directory 'hsr0' with parent 'hsr' already present!
[ 77.204798][ T5924] Cannot create hsr debugfs directory
[ 78.828818][ T5146] Bluetooth: hci0: command tx timeout
[ 79.385430][ T768] bridge_slave_1: left allmulticast mode
[ 79.392966][ T768] bridge_slave_1: left promiscuous mode
[ 79.399801][ T768] bridge0: port 2(bridge_slave_1) entered disabled state
[ 79.414825][ T768] bridge_slave_0: left allmulticast mode
[ 79.420618][ T768] bridge_slave_0: left promiscuous mode
[ 79.426300][ T768] bridge0: port 1(bridge_slave_0) entered disabled state
[ 79.729628][ T768] bond0 (unregistering): (slave bond_slave_0): Releasing backup interface
[ 79.742640][ T768] bond0 (unregistering): (slave bond_slave_1): Releasing backup interface
[ 79.753017][ T768] bond0 (unregistering): Released all slaves
[ 79.892147][ T768] hsr_slave_0: left promiscuous mode
[ 79.899634][ T768] hsr_slave_1: left promiscuous mode
[ 79.905619][ T768] batman_adv: batadv0: Interface deactivated: batadv_slave_0
[ 79.913870][ T768] batman_adv: batadv0: Removing interface: batadv_slave_0
[ 79.922730][ T768] batman_adv: batadv0: Interface deactivated: batadv_slave_1
[ 79.934653][ T768] batman_adv: batadv0: Removing interface: batadv_slave_1
[ 79.952787][ T768] veth1_macvtap: left promiscuous mode
[ 79.959105][ T768] veth0_macvtap: left promiscuous mode
[ 79.964762][ T768] veth1_vlan: left promiscuous mode
[ 79.970637][ T768] veth0_vlan: left promiscuous mode
[ 80.369761][ T768] team0 (unregistering): Port device team_slave_1 removed
[ 80.404676][ T768] team0 (unregistering): Port device team_slave_0 removed
[ 80.813050][ T5924] netdevsim netdevsim0 netdevsim0: renamed from eth0
[ 80.846314][ T5924] netdevsim netdevsim0 netdevsim1: renamed from eth1
[ 80.867147][ T5924] netdevsim netdevsim0 netdevsim2: renamed from eth2
[ 80.877104][ T5924] netdevsim netdevsim0 netdevsim3: renamed from eth3
[ 80.910976][ T5146] Bluetooth: hci0: command tx timeout
[ 81.003190][ T5924] 8021q: adding VLAN 0 to HW filter on device bond0
[ 81.037204][ T5924] 8021q: adding VLAN 0 to HW filter on device team0
[ 81.059292][ T11] bridge0: port 1(bridge_slave_0) entered blocking state
[ 81.066421][ T11] bridge0: port 1(bridge_slave_0) entered forwarding state
[ 81.083510][ T3581] bridge0: port 2(bridge_slave_1) entered blocking state
[ 81.090678][ T3581] bridge0: port 2(bridge_slave_1) entered forwarding state
[ 81.292195][ T768]
[ 81.294581][ T768] ======================================================
[ 81.301707][ T768] WARNING: possible circular locking dependency detected
[ 81.308856][ T768] 6.13.0-syzkaller-g21266b8df522-dirty #0 Not tainted
[ 81.315640][ T768] ------------------------------------------------------
[ 81.322674][ T768] kworker/u8:5/768 is trying to acquire lock:
[ 81.328756][ T768] ffffffff8fed5628 (rtnl_mutex){+.+.}-{4:4}, at: unregister_netdevice_many_notify+0x1a51/0x21a0
[ 81.339251][ T768]
[ 81.339251][ T768] but task is already holding lock:
[ 81.339480][ T5924] 8021q: adding VLAN 0 to HW filter on device batadv0
[ 81.346611][ T768] ffff888071950768 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: ieee80211_remove_interfaces+0xf1/0x720
[ 81.363937][ T768]
[ 81.363937][ T768] which lock already depends on the new lock.
[ 81.363937][ T768]
[ 81.374536][ T768]
[ 81.374536][ T768] the existing dependency chain (in reverse order) is:
[ 81.376998][ T5924] veth0_vlan: entered promiscuous mode
[ 81.383716][ T768]
[ 81.383716][ T768] -> #1 (&rdev->wiphy.mtx){+.+.}-{4:4}:
[ 81.383747][ T768] __mutex_lock+0x19b/0xb10
[ 81.383769][ T768] wiphy_register+0x1c6b/0x2860
[ 81.394705][ T5924] veth1_vlan: entered promiscuous mode
[ 81.396991][ T768] ieee80211_register_hw+0x23ff/0x3ff0
[ 81.418951][ T768] mac80211_hwsim_new_radio+0x2c47/0x56c0
[ 81.419880][ T5924] veth0_macvtap: entered promiscuous mode
[ 81.425209][ T768] init_mac80211_hwsim+0x432/0x8c0
[ 81.433965][ T5924] veth1_macvtap: entered promiscuous mode
[ 81.436970][ T768] do_one_initcall+0x128/0x630
[ 81.447996][ T768] kernel_init_freeable+0x58f/0x8b0
[ 81.452139][ T5924] batman_adv: batadv0: Interface activated: batadv_slave_0
[ 81.453824][ T768] kernel_init+0x1c/0x2b0
[ 81.465598][ T5924] batman_adv: batadv0: Interface activated: batadv_slave_1
[ 81.465866][ T768] ret_from_fork+0x45/0x80
[ 81.477299][ T5924] netdevsim netdevsim0 netdevsim0: set [1, 0] type 2 family 0 port 6081 - 0
[ 81.477980][ T768] ret_from_fork_asm+0x1a/0x30
[ 81.478015][ T768]
[ 81.478015][ T768] -> #0 (rtnl_mutex
[ 81.486868][ T5924] netdevsim netdevsim0 netdevsim1: set [1, 0] type 2 family 0 port 6081 - 0
[ 81.491954][ T768] ){+.+.}-{4:4}:
[ 81.491975][ T768] __lock_acquire+0x249e/0x3c40
[ 81.491998][ T768] lock_acquire.part.0+0x11b/0x380
[ 81.492015][ T768] __mutex_lock+0x19b/0xb10
[ 81.492032][ T768] unregister_netdevice_many_notify+0x1a51/0x21a0
[ 81.492056][ T768] unregister_netdevice_queue+0x307/0x3f0
[ 81.492079][ T768] _cfg80211_unregister_wdev+0x64b/0x830
[ 81.492106][ T768] ieee80211_remove_interfaces+0x34f/0x720
[ 81.500780][ T5924] netdevsim netdevsim0 netdevsim2: set [1, 0] type 2 family 0 port 6081 - 0
[ 81.506721][ T768] ieee80211_unregister_hw+0x55/0x3a0
[ 81.510591][ T5924] netdevsim netdevsim0 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0
[ 81.515698][ T768] mac80211_hwsim_del_radio+0x268/0x370
[ 81.581363][ T768] hwsim_exit_net+0x33f/0x6d0
[ 81.586575][ T768] ops_exit_list+0xb0/0x180
[ 81.591689][ T768] cleanup_net+0x5c6/0xbf0
[ 81.596654][ T768] process_one_work+0x958/0x1b30
[ 81.602212][ T768] worker_thread+0x6c8/0xf00
[ 81.607334][ T768] kthread+0x3af/0x750
[ 81.611929][ T768] ret_from_fork+0x45/0x80
[ 81.616869][ T768] ret_from_fork_asm+0x1a/0x30
[ 81.622168][ T768]
[ 81.622168][ T768] other info that might help us debug this:
[ 81.622168][ T768]
[ 81.632518][ T768] Possible unsafe locking scenario:
[ 81.632518][ T768]
[ 81.639986][ T768] CPU0 CPU1
[ 81.645346][ T768] ---- ----
[ 81.650747][ T768] lock(&rdev->wiphy.mtx);
[ 81.655351][ T768] lock(rtnl_mutex);
[ 81.662043][ T768] lock(&rdev->wiphy.mtx);
[ 81.669183][ T768] lock(rtnl_mutex);
[ 81.673173][ T768]
[ 81.673173][ T768] *** DEADLOCK ***
[ 81.673173][ T768]
[ 81.681394][ T768] 4 locks held by kworker/u8:5/768:
[ 81.686582][ T768] #0: ffff88801bef5948 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x12cd/0x1b30
[ 81.696991][ T768] #1: ffffc900034b7d18 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x8bb/0x1b30
[ 81.706948][ T768] #2: ffffffff8febf610 (pernet_ops_rwsem){++++}-{4:4}, at: cleanup_net+0xca/0xbf0
[ 81.716358][ T768] #3: ffff888071950768 (&rdev->wiphy.mtx){+.+.}-{4:4}, at: ieee80211_remove_interfaces+0xf1/0x720
[ 81.727169][ T768]
[ 81.727169][ T768] stack backtrace:
[ 81.733068][ T768] CPU: 1 UID: 0 PID: 768 Comm: kworker/u8:5 Not tainted 6.13.0-syzkaller-g21266b8df522-dirty #0
[ 81.733091][ T768] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
[ 81.733106][ T768] Workqueue: netns cleanup_net
[ 81.733138][ T768] Call Trace:
[ 81.733144][ T768] <TASK>
[ 81.733152][ T768] dump_stack_lvl+0x116/0x1f0
[ 81.733185][ T768] print_circular_bug+0x490/0x760
[ 81.733216][ T768] check_noncircular+0x31a/0x400
[ 81.733243][ T768] ? __pfx_check_noncircular+0x10/0x10
[ 81.733272][ T768] ? lockdep_lock+0x1b8/0x200
[ 81.733295][ T768] ? __pfx_lockdep_lock+0x10/0x10
[ 81.733317][ T768] ? lockdep_hardirqs_on+0x7c/0x110
[ 81.733344][ T768] __lock_acquire+0x249e/0x3c40
[ 81.733365][ T768] ? __pfx___lock_acquire+0x10/0x10
[ 81.733382][ T768] ? synchronize_rcu_expedited+0x426/0x450
[ 81.733400][ T768] ? __pfx_lock_release+0x10/0x10
[ 81.733418][ T768] lock_acquire.part.0+0x11b/0x380
[ 81.733435][ T768] ? unregister_netdevice_many_notify+0x1a51/0x21a0
[ 81.733457][ T768] ? __pfx_lock_acquire.part.0+0x10/0x10
[ 81.733475][ T768] ? rcu_is_watching+0x12/0xc0
[ 81.733497][ T768] ? trace_lock_acquire+0x14e/0x1f0
[ 81.733520][ T768] ? unregister_netdevice_many_notify+0x1a51/0x21a0
[ 81.733541][ T768] ? lock_acquire+0x2f/0xb0
[ 81.733556][ T768] ? unregister_netdevice_many_notify+0x1a51/0x21a0
[ 81.733577][ T768] __mutex_lock+0x19b/0xb10
[ 81.733604][ T768] ? unregister_netdevice_many_notify+0x1a51/0x21a0
[ 81.733625][ T768] ? unregister_netdevice_many_notify+0x1a51/0x21a0
[ 81.733646][ T768] ? __pfx___mutex_lock+0x10/0x10
[ 81.733662][ T768] ? __pfx_synchronize_rcu_expedited+0x10/0x10
[ 81.733683][ T768] ? __pfx_wait_rcu_exp_gp+0x10/0x10
[ 81.733700][ T768] ? __pfx___might_resched+0x10/0x10
[ 81.733718][ T768] ? unregister_netdevice_many_notify+0x959/0x21a0
[ 81.733740][ T768] ? unregister_netdevice_many_notify+0x1a51/0x21a0
[ 81.733759][ T768] ? rtnl_lock+0x9/0x20
[ 81.733778][ T768] unregister_netdevice_many_notify+0x1a51/0x21a0
[ 81.733802][ T768] ? __pfx_unregister_netdevice_many_notify+0x10/0x10
[ 81.733824][ T768] ? find_held_lock+0x2d/0x110
[ 81.733848][ T768] ? kernfs_remove_by_name_ns+0xc4/0x130
[ 81.733873][ T768] ? __pfx_lock_release+0x10/0x10
[ 81.733889][ T768] ? __call_rcu_common.constprop.0+0x3ea/0x870
[ 81.733911][ T768] unregister_netdevice_queue+0x307/0x3f0
[ 81.733931][ T768] ? __pfx_unregister_netdevice_queue+0x10/0x10
[ 81.733954][ T768] _cfg80211_unregister_wdev+0x64b/0x830
[ 81.733980][ T768] ieee80211_remove_interfaces+0x34f/0x720
[ 81.734010][ T768] ? __pfx_ieee80211_remove_interfaces+0x10/0x10
[ 81.734041][ T768] ieee80211_unregister_hw+0x55/0x3a0
[ 81.734062][ T768] mac80211_hwsim_del_radio+0x268/0x370
[ 81.734088][ T768] ? __pfx_mac80211_hwsim_del_radio+0x10/0x10
[ 81.734115][ T768] ? __local_bh_enable_ip+0xa4/0x120
[ 81.734136][ T768] hwsim_exit_net+0x33f/0x6d0
[ 81.734163][ T768] ? __pfx_hwsim_exit_net+0x10/0x10
[ 81.734189][ T768] ? __pfx___might_resched+0x10/0x10
[ 81.734207][ T768] ? ip_vs_sync_net_cleanup+0x72/0xb0
[ 81.734228][ T768] ? __ip_vs_dev_cleanup_batch+0xb1/0x290
[ 81.734246][ T768] ? __pfx_hwsim_exit_net+0x10/0x10
[ 81.734272][ T768] ops_exit_list+0xb0/0x180
[ 81.734290][ T768] cleanup_net+0x5c6/0xbf0
[ 81.734310][ T768] ? __pfx_cleanup_net+0x10/0x10
[ 81.734331][ T768] ? lock_acquire+0x2f/0xb0
[ 81.734346][ T768] ? process_one_work+0x8bb/0x1b30
[ 81.734374][ T768] process_one_work+0x958/0x1b30
[ 81.734404][ T768] ? __pfx_cleanup_net+0x10/0x10
[ 81.734422][ T768] ? __pfx_process_one_work+0x10/0x10
[ 81.734448][ T768] ? rcu_is_watching+0x12/0xc0
[ 81.734472][ T768] ? assign_work+0x1a0/0x250
[ 81.734498][ T768] worker_thread+0x6c8/0xf00
[ 81.734527][ T768] ? __kthread_parkme+0x148/0x220
[ 81.734550][ T768] ? __pfx_worker_thread+0x10/0x10
[ 81.734576][ T768] kthread+0x3af/0x750
[ 81.734606][ T768] ? __pfx_kthread+0x10/0x10
[ 81.734630][ T768] ? lock_acquire+0x2f/0xb0
[ 81.734648][ T768] ? __pfx_kthread+0x10/0x10
[ 81.734672][ T768] ret_from_fork+0x45/0x80
[ 81.734690][ T768] ? __pfx_kthread+0x10/0x10
[ 81.734715][ T768] ret_from_fork_asm+0x1a/0x30
[ 81.734746][ T768] </TASK>
[ 82.205328][ T5924] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht'
[ 82.988060][ T5146] Bluetooth: hci0: command tx timeout
[ 85.068171][ T5146] Bluetooth: hci0: command tx timeout
[ 87.233907][ T974] cfg80211: failed to load regulatory.db
syzkaller build log:
go env (err=<nil>)
GO111MODULE='auto'
GOARCH='amd64'
GOBIN=''
GOCACHE='/syzkaller/.cache/go-build'
GOENV='/syzkaller/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/syzkaller/jobs/linux/gopath/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/syzkaller/jobs/linux/gopath'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.22.7'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/syzkaller/jobs/linux/gopath/src/github.com/google/syzkaller/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build744164607=/tmp/go-build -gno-record-gcc-switches'
git status (err=<nil>)
HEAD detached at 6dbc6a9bc7
nothing to commit, working tree clean
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
Makefile:31: run command via tools/syz-env for best compatibility, see:
Makefile:32: https://github.com/google/syzkaller/blob/master/docs/contributing.md#using-syz-env
go list -f '{{.Stale}}' ./sys/syz-sysgen | grep -q false || go install ./sys/syz-sysgen
make .descriptions
tput: No value for $TERM and no -T specified
tput: No value for $TERM and no -T specified
Makefile:31: run command via tools/syz-env for best compatibility, see:
Makefile:32: https://github.com/google/syzkaller/blob/master/docs/contributing.md#using-syz-env
bin/syz-sysgen
go fmt ./sys/... >/dev/null
touch .descriptions
GOOS=linux GOARCH=amd64 go build "-ldflags=-s -w -X github.com/google/syzkaller/prog.GitRevision=6dbc6a9bc76e06852841ed5c5bdbb78409b17f53 -X 'github.com/google/syzkaller/prog.gitRevisionDate=20250110-142744'" "-tags=syz_target syz_os_linux syz_arch_amd64 " -o ./bin/linux_amd64/syz-execprog github.com/google/syzkaller/tools/syz-execprog
mkdir -p ./bin/linux_amd64
g++ -o ./bin/linux_amd64/syz-executor executor/executor.cc \
-m64 -O2 -pthread -Wall -Werror -Wparentheses -Wunused-const-variable -Wframe-larger-than=16384 -Wno-stringop-overflow -Wno-array-bounds -Wno-format-overflow -Wno-unused-but-set-variable -Wno-unused-command-line-argument -static-pie -std=c++17 -I. -Iexecutor/_include -fpermissive -w -DGOOS_linux=1 -DGOARCH_amd64=1 \
-DHOSTGOOS_linux=1 -DGIT_REVISION=\"6dbc6a9bc76e06852841ed5c5bdbb78409b17f53\"
/usr/bin/ld: /tmp/ccJVchnk.o: in function `Connection::Connect(char const*, char const*)':
executor.cc:(.text._ZN10Connection7ConnectEPKcS1_[_ZN10Connection7ConnectEPKcS1_]+0x104): warning: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
Error text is too large and was truncated, full error text is at:
https://syzkaller.appspot.com/x/error.txt?x=1733f964580000
Tested on:
commit: 21266b8d Merge tag 'AT_EXECVE_CHECK-v6.14-rc1' of git:..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=77593a73383cac88
dashboard link: https://syzkaller.appspot.com/bug?extid=83976e47ec1ef91e66f1
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=15b85ab0580000
^ permalink raw reply [flat|nested] 138+ messages in thread
* Re: [syzbot] [usb?] general protection fault in status_show
2025-01-17 6:14 [syzbot] [usb?] general protection fault in status_show syzbot
` (2 preceding siblings ...)
2025-01-23 11:31 ` Hillf Danton
@ 2025-01-24 11:17 ` Hillf Danton
2025-01-24 11:32 ` syzbot
2025-01-25 10:23 ` Hillf Danton
4 siblings, 1 reply; 138+ messages in thread
From: Hillf Danton @ 2025-01-24 11:17 UTC (permalink / raw)
To: syzbot; +Cc: linux-kernel, syzkaller-bugs
On Thu, 16 Jan 2025 22:14:23 -0800
> syzbot found the following issue on:
>
> HEAD commit: be548645527a Merge tag 'for-linus' of git://git.kernel.org..
> git tree: upstream
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12d51cb0580000
#syz test upstream master
--- x/drivers/usb/usbip/vhci_sysfs.c
+++ y/drivers/usb/usbip/vhci_sysfs.c
@@ -76,6 +76,8 @@ static ssize_t status_show_vhci(int pdev
}
hcd = platform_get_drvdata(pdev);
+ if (!usb_hcd_is_primary_hcd(hcd))
+ return 0;
vhci_hcd = hcd_to_vhci_hcd(hcd);
vhci = vhci_hcd->vhci;
--- x/net/core/dev.c
+++ y/net/core/dev.c
@@ -10260,14 +10260,19 @@ static bool from_cleanup_net(void)
#endif
}
+static unsigned long extra_netdev_locks = 1;
static void rtnl_drop_if_cleanup_net(void)
{
+ if (extra_netdev_locks)
+ return;
if (from_cleanup_net())
__rtnl_unlock();
}
static void rtnl_acquire_if_cleanup_net(void)
{
+ if (extra_netdev_locks)
+ return;
if (from_cleanup_net())
rtnl_lock();
}
--
^ permalink raw reply [flat|nested] 138+ messages in thread
* Re: [syzbot] [usb?] general protection fault in status_show
2025-01-24 11:17 ` Hillf Danton
@ 2025-01-24 11:32 ` syzbot
0 siblings, 0 replies; 138+ messages in thread
From: syzbot @ 2025-01-24 11:32 UTC (permalink / raw)
To: hdanton, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
general protection fault in usb_hcd_is_primary_hcd
Oops: general protection fault, probably for non-canonical address 0xdffffc000000007a: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x00000000000003d0-0x00000000000003d7]
CPU: 0 UID: 0 PID: 6619 Comm: syz.0.16 Not tainted 6.13.0-syzkaller-gbc8198dc7ebc-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
RIP: 0010:usb_hcd_is_primary_hcd+0x26/0x70 drivers/usb/core/hcd.c:2699
Code: 90 90 90 90 f3 0f 1e fa 55 53 48 89 fb e8 72 77 b0 fa 48 8d bb d0 03 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 75 3b 48 8b ab d0 03 00 00 48 85 ed 74 1c e8 43 77 b0
RSP: 0018:ffffc90003257ac0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff875ac534
RDX: 000000000000007a RSI: ffffffff86e896be RDI: 00000000000003d0
RBP: ffff888033124000 R08: 0000000000000005 R09: 0000000000000000
R10: 000000000000000f R11: 64666b636f732020 R12: 1ffff9200064af61
R13: 0000000000000000 R14: ffff88803312402d R15: 000000000000000f
FS: 00007f4de32746c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2ee5ffff CR3: 000000001e2cc000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
status_show_vhci drivers/usb/usbip/vhci_sysfs.c:79 [inline]
status_show+0x2e1/0x5e0 drivers/usb/usbip/vhci_sysfs.c:162
dev_attr_show+0x53/0xe0 drivers/base/core.c:2423
sysfs_kf_seq_show+0x223/0x3e0 fs/sysfs/file.c:59
seq_read_iter+0x4f4/0x12b0 fs/seq_file.c:230
kernfs_fop_read_iter+0x414/0x580 fs/kernfs/file.c:279
new_sync_read fs/read_write.c:484 [inline]
vfs_read+0x886/0xbf0 fs/read_write.c:565
ksys_read+0x12b/0x250 fs/read_write.c:708
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4de2385d29
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4de3274038 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007f4de2575fa0 RCX: 00007f4de2385d29
RDX: 0000000000000062 RSI: 0000000020001080 RDI: 0000000000000003
RBP: 00007f4de2401b08 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f4de2575fa0 R15: 00007ffe71b07568
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:usb_hcd_is_primary_hcd+0x26/0x70 drivers/usb/core/hcd.c:2699
Code: 90 90 90 90 f3 0f 1e fa 55 53 48 89 fb e8 72 77 b0 fa 48 8d bb d0 03 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 75 3b 48 8b ab d0 03 00 00 48 85 ed 74 1c e8 43 77 b0
RSP: 0018:ffffc90003257ac0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff875ac534
RDX: 000000000000007a RSI: ffffffff86e896be RDI: 00000000000003d0
RBP: ffff888033124000 R08: 0000000000000005 R09: 0000000000000000
R10: 000000000000000f R11: 64666b636f732020 R12: 1ffff9200064af61
R13: 0000000000000000 R14: ffff88803312402d R15: 000000000000000f
FS: 00007f4de32746c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5e99d20440 CR3: 000000001e2cc000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 90 nop
1: 90 nop
2: 90 nop
3: 90 nop
4: f3 0f 1e fa endbr64
8: 55 push %rbp
9: 53 push %rbx
a: 48 89 fb mov %rdi,%rbx
d: e8 72 77 b0 fa call 0xfab07784
12: 48 8d bb d0 03 00 00 lea 0x3d0(%rbx),%rdi
19: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
20: fc ff df
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 75 3b jne 0x6b
30: 48 8b ab d0 03 00 00 mov 0x3d0(%rbx),%rbp
37: 48 85 ed test %rbp,%rbp
3a: 74 1c je 0x58
3c: e8 .byte 0xe8
3d: 43 77 b0 rex.XB ja 0xfffffff0
Tested on:
commit: bc8198dc Merge tag 'sched_ext-for-6.14' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=132315df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=77593a73383cac88
dashboard link: https://syzkaller.appspot.com/bug?extid=83976e47ec1ef91e66f1
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=1041e9f8580000
^ permalink raw reply [flat|nested] 138+ messages in thread
* Re: [syzbot] [usb?] general protection fault in status_show
2025-01-17 6:14 [syzbot] [usb?] general protection fault in status_show syzbot
` (3 preceding siblings ...)
2025-01-24 11:17 ` Hillf Danton
@ 2025-01-25 10:23 ` Hillf Danton
2025-01-25 10:44 ` syzbot
4 siblings, 1 reply; 138+ messages in thread
From: Hillf Danton @ 2025-01-25 10:23 UTC (permalink / raw)
To: syzbot; +Cc: linux-kernel, syzkaller-bugs
On Thu, 16 Jan 2025 22:14:23 -0800
> syzbot found the following issue on:
>
> HEAD commit: be548645527a Merge tag 'for-linus' of git://git.kernel.org..
> git tree: upstream
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12d51cb0580000
#syz test upstream master
--- x/drivers/usb/usbip/vhci_sysfs.c
+++ y/drivers/usb/usbip/vhci_sysfs.c
@@ -76,6 +76,8 @@ static ssize_t status_show_vhci(int pdev
}
hcd = platform_get_drvdata(pdev);
+ if (!hcd || !usb_hcd_is_primary_hcd(hcd))
+ return 0;
vhci_hcd = hcd_to_vhci_hcd(hcd);
vhci = vhci_hcd->vhci;
--- x/net/core/dev.c
+++ y/net/core/dev.c
@@ -10260,14 +10260,19 @@ static bool from_cleanup_net(void)
#endif
}
+static unsigned long extra_netdev_locks = 1;
static void rtnl_drop_if_cleanup_net(void)
{
+ if (extra_netdev_locks)
+ return;
if (from_cleanup_net())
__rtnl_unlock();
}
static void rtnl_acquire_if_cleanup_net(void)
{
+ if (extra_netdev_locks)
+ return;
if (from_cleanup_net())
rtnl_lock();
}
--
^ permalink raw reply [flat|nested] 138+ messages in thread
* Re: [syzbot] [usb?] general protection fault in status_show
2025-01-25 10:23 ` Hillf Danton
@ 2025-01-25 10:44 ` syzbot
0 siblings, 0 replies; 138+ messages in thread
From: syzbot @ 2025-01-25 10:44 UTC (permalink / raw)
To: hdanton, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
lost connection to test machine
Tested on:
commit: b46c89c0 Merge tag 'spi-fix-v6.14-merge-window' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1292d5df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=d00941da012c109
dashboard link: https://syzkaller.appspot.com/bug?extid=83976e47ec1ef91e66f1
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=13b799f8580000
^ permalink raw reply [flat|nested] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ messages in thread
From: Arnaud Lecomte @ 2025-04-07 14:17 UTC (permalink / raw)
To: syzbot+29fc8991b0ecb186cf40
Cc: andrew+netdev, davem, edumazet, kuba, linux-kernel, linux-ppp,
netdev, pabeni, syzkaller-bugs
Author: contact@arnaud-lcm.com
#syz test
diff --git a/drivers/net/ppp/ppp_synctty.c b/drivers/net/ppp/ppp_synctty.c
index 644e99fc3623..520d895acc60 100644
--- a/drivers/net/ppp/ppp_synctty.c
+++ b/drivers/net/ppp/ppp_synctty.c
@@ -506,6 +506,11 @@ ppp_sync_txmunge(struct syncppp *ap, struct sk_buff *skb)
unsigned char *data;
int islcp;
+ /* Ensure we can safely access protocol field and LCP code */
+ if (!skb || !pskb_may_pull(skb, 3)) {
+ kfree_skb(skb);
+ return NULL;
+ }
data = skb->data;
proto = get_unaligned_be16(data);
^ permalink raw reply [flat|nested] 138+ messages in thread
* Re: [syzbot]
2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
@ 2025-04-07 14:17 ` syzbot
0 siblings, 0 replies; 138+ 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] 138+ 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; 138+ messages in thread
From: Arnaud Lecomte @ 2025-04-07 14:17 UTC (permalink / raw)
To: syzbot+29fc8991b0ecb186cf40
Cc: andrew+netdev, davem, edumazet, kuba, linux-kernel, linux-ppp,
netdev, pabeni, syzkaller-bugs
Author: contact@arnaud-lcm.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
diff --git a/drivers/net/ppp/ppp_synctty.c b/drivers/net/ppp/ppp_synctty.c
index 644e99fc3623..520d895acc60 100644
--- a/drivers/net/ppp/ppp_synctty.c
+++ b/drivers/net/ppp/ppp_synctty.c
@@ -506,6 +506,11 @@ ppp_sync_txmunge(struct syncppp *ap, struct sk_buff *skb)
unsigned char *data;
int islcp;
+ /* Ensure we can safely access protocol field and LCP code */
+ if (!skb || !pskb_may_pull(skb, 3)) {
+ kfree_skb(skb);
+ return NULL;
+ }
data = skb->data;
proto = get_unaligned_be16(data);
^ permalink raw reply [flat|nested] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ messages in thread
* Re: [syzbot]
[not found] <mailman.217.1706634262.2961.pvrusb2@isely.net>
@ 2024-02-15 16:26 ` syzbot
0 siblings, 0 replies; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ 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; 138+ 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] 138+ messages in thread
* Re: [syzbot]
2022-02-10 19:17 [syzbot] general protection fault in blk_mq_free_rqs syzbot
@ 2023-11-10 18:56 ` syzbot
0 siblings, 0 replies; 138+ 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] 138+ messages in thread
end of thread, other threads:[~2025-06-19 21:00 UTC | newest]
Thread overview: 138+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-01-17 6:14 [syzbot] [usb?] general protection fault in status_show syzbot
2025-01-17 15:41 ` [syzbot] syzbot
2025-01-22 22:19 ` [syzbot] Re: [syzbot] [usb?] general protection fault in status_show syzbot
2025-01-23 11:31 ` Hillf Danton
2025-01-23 11:45 ` syzbot
2025-01-24 11:17 ` Hillf Danton
2025-01-24 11:32 ` syzbot
2025-01-25 10:23 ` Hillf Danton
2025-01-25 10:44 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-06-12 7:52 [syzbot] [bcachefs?] WARNING in __init_work (2) syzbot
2025-06-19 20:54 ` [syzbot] syzbot
2025-06-10 19:15 [syzbot] [bcachefs?] divide error in bch2_sb_members_v2_to_text syzbot
2025-06-19 21:00 ` [syzbot] syzbot
2025-06-08 5:52 [syzbot] [bcachefs?] kernel BUG in vfs_get_tree (2) syzbot
2025-06-19 20:57 ` [syzbot] syzbot
2025-05-31 15:09 [syzbot] [bcachefs?] WARNING in lookup_object_or_alloc syzbot
2025-06-19 20:54 ` [syzbot] syzbot
2025-05-26 10:41 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_sb_members_v2_to_text syzbot
2025-06-08 15:33 ` [syzbot] syzbot
2025-05-26 8:50 [syzbot] [bcachefs?] WARNING in rhashtable_init_noprof syzbot
2025-06-08 15:41 ` [syzbot] syzbot
2025-04-28 17:04 [syzbot] [bcachefs?] UBSAN: array-index-out-of-bounds in bch2_sb_downgrade_update syzbot
2025-06-08 16:01 ` [syzbot] syzbot
2025-04-08 11:53 [syzbot] [bcachefs?] WARNING in bch2_dev_free syzbot
2025-04-18 0:37 ` [syzbot] syzbot
2025-03-31 14:06 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_copygc (2) syzbot
2025-04-01 4:10 ` [syzbot] syzbot
2025-03-31 2:14 [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in __kfifo_alloc syzbot
2025-04-01 10:18 ` [syzbot] syzbot
2025-04-01 10:24 ` [syzbot] syzbot
2025-04-01 11:04 ` [syzbot] syzbot
2025-03-30 16:49 [syzbot] [pci?] upstream test error: BUG: unable to handle kernel NULL pointer dereference in msix_prepare_msi_desc syzbot
2025-04-03 7:06 ` [syzbot] syzbot
2025-03-30 10:15 [syzbot] [pci?] upstream test error: general protection fault in msix_prepare_msi_desc syzbot
2025-04-03 7:06 ` [syzbot] syzbot
2025-03-09 4:20 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_extent_crc_append (2) syzbot
2025-04-01 3:55 ` [syzbot] syzbot
2025-02-23 6:02 [syzbot] linux-next build error (20) syzbot
2025-04-14 14:48 ` [syzbot] syzbot
2025-02-17 11:55 [syzbot] [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-17 11:55 [syzbot] [can?] WARNING in ucan_probe syzbot
2025-02-17 17:59 ` [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-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?] kernel BUG in bch2_journal_pin_set syzbot
2024-11-28 3:23 ` [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:05 [syzbot] [bcachefs?] kernel BUG in bch2_evacuate_bucket syzbot
2024-11-29 0:39 ` [syzbot] syzbot
2024-11-25 3:10 [syzbot] [bcachefs?] kernel BUG in __bch2_journal_pin_put syzbot
2024-11-28 3:00 ` [syzbot] syzbot
2024-11-22 18:44 [syzbot] [bcachefs?] KMSAN: uninit-value in rw_aux_tree_set (2) syzbot
2025-04-01 4:09 ` [syzbot] syzbot
2024-11-22 18:44 [syzbot] [bcachefs?] kernel BUG in bch2_btree_pos_to_text (2) syzbot
2024-11-25 3:59 ` [syzbot] syzbot
2024-11-22 15:15 [syzbot] [bcachefs?] kernel BUG in bch2_btree_root_read syzbot
2024-11-25 6:53 ` [syzbot] syzbot
2024-11-22 14:42 [syzbot] [netfilter?] KMSAN: uninit-value in ip6table_mangle_hook (3) syzbot
2024-12-14 22:16 ` [syzbot] syzbot
2024-12-14 22:21 ` [syzbot] syzbot
2024-12-15 2:34 ` [syzbot] syzbot
2024-11-21 12:40 [syzbot] [bcachefs?] kernel BUG in bch2_btree_node_lock_write syzbot
2024-11-28 3:12 ` [syzbot] syzbot
2024-11-19 7:33 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_inode_v3_validate syzbot
2025-04-01 4:08 ` [syzbot] syzbot
2024-11-18 21:41 [syzbot] [bcachefs?] kernel BUG in bch2_bucket_alloc_trans (3) syzbot
2024-11-25 6:54 ` [syzbot] syzbot
2024-11-17 8:54 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_alloc_v4_validate (2) syzbot
2025-04-01 4:00 ` [syzbot] syzbot
2024-11-17 8:54 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_iter_init (2) syzbot
2025-04-01 4:07 ` [syzbot] syzbot
2024-11-12 3:25 [syzbot] [bcachefs?] possible deadlock in bch2_alloc_sectors_start_trans syzbot
2024-11-29 0:34 ` [syzbot] syzbot
2024-11-11 0:28 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_check_topology syzbot
2025-04-01 4:10 ` [syzbot] syzbot
2024-11-09 15:43 [syzbot] [bcachefs?] kernel BUG in __bch2_btree_node_hash_insert syzbot
2024-11-11 3:13 ` [syzbot] syzbot
2024-11-08 15:57 [syzbot] [bcachefs?] kernel BUG in bch2_rechecksum_bio syzbot
2024-11-29 0:32 ` [syzbot] syzbot
2024-11-06 13:58 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bucket_alloc_early syzbot
2025-04-01 4:05 ` [syzbot] syzbot
2024-11-06 13:24 [syzbot] [bcachefs?] kernel BUG in bch2_btree_path_traverse_one syzbot
2024-11-28 3:27 ` [syzbot] syzbot
2024-10-30 16:39 [syzbot] [bcachefs?] kernel BUG in __bkey_unpack_pos syzbot
2024-11-08 5:02 ` [syzbot] syzbot
2024-10-28 15:49 [syzbot] [bcachefs?] kernel BUG in bch2_btree_write_buffer_flush_locked syzbot
2024-11-28 3:21 ` [syzbot] syzbot
2024-10-27 3:54 [syzbot] [bcachefs?] kernel BUG in bch2_inconsistent_error syzbot
2024-11-08 0:48 ` [syzbot] syzbot
2024-10-27 1:10 [syzbot] [bcachefs?] kernel BUG in bch2_bkey_pack_pos_lossy syzbot
2024-11-08 5:11 ` [syzbot] syzbot
2024-10-25 6:49 [syzbot] [bcachefs?] kernel BUG in bch2_trans_node_iter_init syzbot
2024-11-08 3:21 ` [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:48 [syzbot] [bcachefs?] general protection fault in bch2_btree_path_traverse_one syzbot
2024-11-27 8:09 ` [syzbot] syzbot
2024-10-25 6:48 [syzbot] [bcachefs?] kernel BUG in bch2_journal_res_get (2) syzbot
2024-11-08 3:28 ` [syzbot] syzbot
2024-10-24 17:47 [syzbot] [bcachefs?] kernel BUG in bch2_run_recovery_pass syzbot
2024-11-11 4:31 ` [syzbot] syzbot
2024-10-23 18:30 [syzbot] [bcachefs?] possible deadlock in __bch2_trans_relock syzbot
2024-11-28 23:06 ` [syzbot] syzbot
2024-10-23 14:27 [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in validate_sb_layout syzbot
2024-10-26 0:49 ` [syzbot] syzbot
2024-10-23 11:21 [syzbot] [bcachefs?] kernel BUG in bch2_btree_path_level_init (2) syzbot
2024-11-11 3:14 ` [syzbot] syzbot
2024-10-23 4:12 [syzbot] [bcachefs?] kernel BUG in bch2_ptr_swab syzbot
2024-11-11 21:16 ` [syzbot] syzbot
2024-10-21 13:07 [syzbot] [bcachefs?] kernel BUG in bch2_dev_btree_bitmap_mark syzbot
2024-11-08 4:25 ` [syzbot] syzbot
2024-10-21 6:44 [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in bch2_alloc_to_text syzbot
2024-10-26 0:47 ` [syzbot] syzbot
2024-10-21 4:31 [syzbot] [bcachefs?] kernel BUG in __bch2_trans_commit syzbot
2024-11-08 0:18 ` [syzbot] syzbot
2024-10-18 7:37 [syzbot] [bcachefs?] kernel BUG in bch2_fs_btree_cache_exit syzbot
2024-11-11 4:46 ` [syzbot] syzbot
2024-10-03 17:42 [syzbot] [bcachefs?] possible deadlock in bch2_replicas_entry_validate syzbot
2024-10-16 6:42 ` [syzbot] syzbot
2024-10-03 8:10 [syzbot] [bcachefs?] kernel BUG in __bch2_btree_node_write syzbot
2024-11-25 6:52 ` [syzbot] syzbot
2024-09-28 2:13 [syzbot] [bcachefs?] kernel BUG in bch2_fs_btree_write_buffer_exit syzbot
2024-11-08 3:04 ` [syzbot] syzbot
2024-09-18 7:28 [syzbot] [bcachefs?] WARNING in bch2_journal_flush_seq_async syzbot
2024-11-28 22:50 ` [syzbot] syzbot
2024-08-27 2:12 [syzbot] [sound?] WARNING in snd_pcm_open syzbot
2024-09-06 10:33 ` [syzbot] syzbot
2024-07-30 1:14 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in journal_entry_dev_usage_to_text syzbot
2024-11-11 21:03 ` [syzbot] syzbot
2024-07-24 8:59 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in mgmt_remove_adv_monitor_sync syzbot
2024-12-05 1:58 ` [syzbot] syzbot
2024-12-23 22:19 ` [syzbot] syzbot
2024-07-17 13:39 [syzbot] [bcachefs?] general protection fault in bch2_checksum syzbot
2024-11-28 22:59 ` [syzbot] syzbot
2024-07-13 22:54 [syzbot] [bpf?] [trace?] possible deadlock in console_flush_all (3) syzbot
2025-06-19 20:48 ` [syzbot] syzbot
2024-07-10 20:55 [syzbot] [bcachefs?] kernel BUG in bch2_journal_noflush_seq syzbot
2024-11-28 22:12 ` [syzbot] syzbot
2024-06-14 12:16 [syzbot] [crypto?] [bcachefs?] BUG: unable to handle kernel paging request in crypto_skcipher_encrypt syzbot
2024-11-25 7:19 ` [syzbot] syzbot
[not found] <mailman.217.1706634262.2961.pvrusb2@isely.net>
2024-02-15 16:26 ` [syzbot] syzbot
2024-01-12 20:14 [syzbot] upstream build error (21) syzbot
2024-06-20 8:00 ` [syzbot] syzbot
2024-01-05 17:32 [syzbot] [net?] memory leak in ___neigh_create (2) syzbot
2024-09-05 11:54 ` [syzbot] syzbot
2023-11-16 11:09 [syzbot] [kernel?] inconsistent lock state in __lock_task_sighand syzbot
2024-09-06 10:37 ` [syzbot] syzbot
2023-11-15 9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
2023-11-16 2:33 ` [syzbot] syzbot
2023-11-16 3:29 ` [syzbot] syzbot
2023-10-16 7:38 [syzbot] [kernel?] KASAN: slab-use-after-free Read in reweight_entity syzbot
2024-09-06 10:38 ` [syzbot] syzbot
2023-06-05 3:53 [syzbot] [ext4?] WARNING: locking bug in ext4_move_extents syzbot
2024-07-03 7:48 ` [syzbot] syzbot
2022-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
all inboxes | Powered by JetHome®