* INFO: trying to register non-static key in ath9k_htc_rxep
@ 2020-06-18 20:57 syzbot
2020-06-20 10:57 ` syzbot
0 siblings, 1 reply; 9+ messages in thread
From: syzbot @ 2020-06-18 20:57 UTC (permalink / raw)
To: andreyknvl, ath9k-devel, davem, kuba, kvalo, linux-kernel,
linux-usb, linux-wireless, netdev, syzkaller-bugs
Hello,
syzbot found the following crash on:
HEAD commit: b791d1bd Merge tag 'locking-kcsan-2020-06-11' of git://git..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=1522cc25100000
kernel config: https://syzkaller.appspot.com/x/.config?x=16c2467d4b6dbee2
dashboard link: https://syzkaller.appspot.com/bug?extid=4d2d56175b934b9a7bf9
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 0 PID: 355 Comm: syz-executor.2 Not tainted 5.7.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0xf6/0x16e lib/dump_stack.c:118
assign_lock_key kernel/locking/lockdep.c:894 [inline]
register_lock_class+0x1442/0x17e0 kernel/locking/lockdep.c:1206
__lock_acquire+0x101/0x6270 kernel/locking/lockdep.c:4259
lock_acquire+0x18b/0x7c0 kernel/locking/lockdep.c:4959
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x32/0x50 kernel/locking/spinlock.c:159
ath9k_htc_rxep+0x31/0x210 drivers/net/wireless/ath/ath9k/htc_drv_txrx.c:1128
ath9k_htc_rx_msg+0x2d9/0xb00 drivers/net/wireless/ath/ath9k/htc_hst.c:459
ath9k_hif_usb_rx_stream drivers/net/wireless/ath/ath9k/hif_usb.c:638 [inline]
ath9k_hif_usb_rx_cb+0xc76/0x1050 drivers/net/wireless/ath/ath9k/hif_usb.c:671
__usb_hcd_giveback_urb+0x29a/0x550 drivers/usb/core/hcd.c:1650
usb_hcd_giveback_urb+0x368/0x420 drivers/usb/core/hcd.c:1716
dummy_timer+0x125e/0x32b4 drivers/usb/gadget/udc/dummy_hcd.c:1967
call_timer_fn+0x1ac/0x6e0 kernel/time/timer.c:1404
expire_timers kernel/time/timer.c:1449 [inline]
__run_timers kernel/time/timer.c:1773 [inline]
__run_timers kernel/time/timer.c:1740 [inline]
run_timer_softirq+0x5e5/0x14c0 kernel/time/timer.c:1786
__do_softirq+0x21e/0x996 kernel/softirq.c:292
invoke_softirq kernel/softirq.c:373 [inline]
irq_exit+0x178/0x1a0 kernel/softirq.c:413
exiting_irq arch/x86/include/asm/apic.h:546 [inline]
smp_apic_timer_interrupt+0x141/0x540 arch/x86/kernel/apic/apic.c:1107
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:829
</IRQ>
RIP: 0010:arch_local_irq_restore arch/x86/include/asm/irqflags.h:85 [inline]
RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0x3b/0x40 kernel/locking/spinlock.c:191
Code: e8 1a 69 8d fb 48 89 ef e8 42 5d 8e fb f6 c7 02 75 11 53 9d e8 26 e6 ab fb 65 ff 0d 57 e4 68 7a 5b 5d c3 e8 e7 de ab fb 53 9d <eb> ed 0f 1f 00 55 48 89 fd 65 ff 05 3d e4 68 7a 45 31 c9 41 b8 01
RSP: 0018:ffff8881ae06fba0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000000 RBX: 0000000000000246 RCX: 1ffffffff0fd4d4a
RDX: 1ffff11039bbe747 RSI: 0000000000000000 RDI: ffff8881cddf3a38
RBP: ffff8881db228400 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff8881db228480 R14: ffff8881ae06fdf8 R15: ffff8881db228400
unlock_hrtimer_base kernel/time/hrtimer.c:898 [inline]
hrtimer_start_range_ns+0x5cd/0xb50 kernel/time/hrtimer.c:1136
hrtimer_start_expires include/linux/hrtimer.h:435 [inline]
hrtimer_sleeper_start_expires kernel/time/hrtimer.c:1800 [inline]
do_nanosleep+0x1b9/0x650 kernel/time/hrtimer.c:1876
hrtimer_nanosleep+0x1df/0x3a0 kernel/time/hrtimer.c:1932
__do_sys_nanosleep kernel/time/hrtimer.c:1966 [inline]
__se_sys_nanosleep kernel/time/hrtimer.c:1953 [inline]
__x64_sys_nanosleep+0x1dc/0x260 kernel/time/hrtimer.c:1953
do_syscall_64+0xb6/0x5a0 arch/x86/entry/common.c:295
entry_SYSCALL_64_after_hwframe+0x49/0xb3
RIP: 0033:0x45af70
Code: Bad RIP value.
RSP: 002b:00007fff27bba8e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000023
RAX: ffffffffffffffda RBX: 000000000009722e RCX: 000000000045af70
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00007fff27bba8f0
RBP: 00000000000001de R08: 0000000000000001 R09: 0000000001410940
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff27bba940 R14: 000000000009722e R15: 00007fff27bba950
BUG: unable to handle page fault for address: ffffffffffffffc8
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 7026067 P4D 7026067 PUD 7028067 PMD 0
Oops: 0000 [#1] SMP KASAN
CPU: 0 PID: 355 Comm: syz-executor.2 Not tainted 5.7.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:ath9k_htc_rxep+0xb5/0x210 drivers/net/wireless/ath/ath9k/htc_drv_txrx.c:1130
Code: 8b 43 38 48 8d 58 c8 49 39 c4 0f 84 ee 00 00 00 e8 90 fd 61 fe 48 89 d8 48 c1 e8 03 0f b6 04 28 84 c0 74 06 0f 8e 0a 01 00 00 <44> 0f b6 3b 31 ff 44 89 fe e8 cd fe 61 fe 45 84 ff 75 a8 e8 63 fd
RSP: 0018:ffff8881db209870 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffffffffffffffc8 RCX: ffffc900004a7000
RDX: 0000000000040000 RSI: ffffffff82ddb320 RDI: ffff8881db2097e0
RBP: dffffc0000000000 R08: 0000000000000004 R09: ffffed103b6412fd
R10: 0000000000000003 R11: ffffed103b6412fc R12: ffff8881ac34b4d8
R13: ffff8881ac34b0a0 R14: ffff8881ac34b4e8 R15: ffffed10392efc10
FS: 0000000001410940(0000) GS:ffff8881db200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffc8 CR3: 00000001ae02b000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
ath9k_htc_rx_msg+0x2d9/0xb00 drivers/net/wireless/ath/ath9k/htc_hst.c:459
ath9k_hif_usb_rx_stream drivers/net/wireless/ath/ath9k/hif_usb.c:638 [inline]
ath9k_hif_usb_rx_cb+0xc76/0x1050 drivers/net/wireless/ath/ath9k/hif_usb.c:671
__usb_hcd_giveback_urb+0x29a/0x550 drivers/usb/core/hcd.c:1650
usb_hcd_giveback_urb+0x368/0x420 drivers/usb/core/hcd.c:1716
dummy_timer+0x125e/0x32b4 drivers/usb/gadget/udc/dummy_hcd.c:1967
call_timer_fn+0x1ac/0x6e0 kernel/time/timer.c:1404
expire_timers kernel/time/timer.c:1449 [inline]
__run_timers kernel/time/timer.c:1773 [inline]
__run_timers kernel/time/timer.c:1740 [inline]
run_timer_softirq+0x5e5/0x14c0 kernel/time/timer.c:1786
__do_softirq+0x21e/0x996 kernel/softirq.c:292
invoke_softirq kernel/softirq.c:373 [inline]
irq_exit+0x178/0x1a0 kernel/softirq.c:413
exiting_irq arch/x86/include/asm/apic.h:546 [inline]
smp_apic_timer_interrupt+0x141/0x540 arch/x86/kernel/apic/apic.c:1107
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:829
</IRQ>
RIP: 0010:arch_local_irq_restore arch/x86/include/asm/irqflags.h:85 [inline]
RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0x3b/0x40 kernel/locking/spinlock.c:191
Code: e8 1a 69 8d fb 48 89 ef e8 42 5d 8e fb f6 c7 02 75 11 53 9d e8 26 e6 ab fb 65 ff 0d 57 e4 68 7a 5b 5d c3 e8 e7 de ab fb 53 9d <eb> ed 0f 1f 00 55 48 89 fd 65 ff 05 3d e4 68 7a 45 31 c9 41 b8 01
RSP: 0018:ffff8881ae06fba0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000000 RBX: 0000000000000246 RCX: 1ffffffff0fd4d4a
RDX: 1ffff11039bbe747 RSI: 0000000000000000 RDI: ffff8881cddf3a38
RBP: ffff8881db228400 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff8881db228480 R14: ffff8881ae06fdf8 R15: ffff8881db228400
unlock_hrtimer_base kernel/time/hrtimer.c:898 [inline]
hrtimer_start_range_ns+0x5cd/0xb50 kernel/time/hrtimer.c:1136
hrtimer_start_expires include/linux/hrtimer.h:435 [inline]
hrtimer_sleeper_start_expires kernel/time/hrtimer.c:1800 [inline]
do_nanosleep+0x1b9/0x650 kernel/time/hrtimer.c:1876
hrtimer_nanosleep+0x1df/0x3a0 kernel/time/hrtimer.c:1932
__do_sys_nanosleep kernel/time/hrtimer.c:1966 [inline]
__se_sys_nanosleep kernel/time/hrtimer.c:1953 [inline]
__x64_sys_nanosleep+0x1dc/0x260 kernel/time/hrtimer.c:1953
do_syscall_64+0xb6/0x5a0 arch/x86/entry/common.c:295
entry_SYSCALL_64_after_hwframe+0x49/0xb3
RIP: 0033:0x45af70
Code: Bad RIP value.
RSP: 002b:00007fff27bba8e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000023
RAX: ffffffffffffffda RBX: 000000000009722e RCX: 000000000045af70
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00007fff27bba8f0
RBP: 00000000000001de R08: 0000000000000001 R09: 0000000001410940
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff27bba940 R14: 000000000009722e R15: 00007fff27bba950
Modules linked in:
CR2: ffffffffffffffc8
---[ end trace 4488f3a2c836a427 ]---
RIP: 0010:ath9k_htc_rxep+0xb5/0x210 drivers/net/wireless/ath/ath9k/htc_drv_txrx.c:1130
Code: 8b 43 38 48 8d 58 c8 49 39 c4 0f 84 ee 00 00 00 e8 90 fd 61 fe 48 89 d8 48 c1 e8 03 0f b6 04 28 84 c0 74 06 0f 8e 0a 01 00 00 <44> 0f b6 3b 31 ff 44 89 fe e8 cd fe 61 fe 45 84 ff 75 a8 e8 63 fd
RSP: 0018:ffff8881db209870 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffffffffffffffc8 RCX: ffffc900004a7000
RDX: 0000000000040000 RSI: ffffffff82ddb320 RDI: ffff8881db2097e0
RBP: dffffc0000000000 R08: 0000000000000004 R09: ffffed103b6412fd
R10: 0000000000000003 R11: ffffed103b6412fc R12: ffff8881ac34b4d8
R13: ffff8881ac34b0a0 R14: ffff8881ac34b4e8 R15: ffffed10392efc10
FS: 0000000001410940(0000) GS:ffff8881db200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffc8 CR3: 00000001ae02b000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: INFO: trying to register non-static key in ath9k_htc_rxep
2020-06-18 20:57 INFO: trying to register non-static key in ath9k_htc_rxep syzbot
@ 2020-06-20 10:57 ` syzbot
0 siblings, 0 replies; 9+ messages in thread
From: syzbot @ 2020-06-20 10:57 UTC (permalink / raw)
To: andreyknvl, ath9k-devel, davem, kuba, kvalo, linux-kernel,
linux-usb, linux-wireless, netdev, syzkaller-bugs
syzbot has found a reproducer for the following crash on:
HEAD commit: f8f02d5c USB: OTG: rename product list of devices
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=15fd18a5100000
kernel config: https://syzkaller.appspot.com/x/.config?x=f1981539b6376b73
dashboard link: https://syzkaller.appspot.com/bug?extid=4d2d56175b934b9a7bf9
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14519481100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=110318e9100000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.8.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0xf6/0x16e lib/dump_stack.c:118
assign_lock_key kernel/locking/lockdep.c:894 [inline]
register_lock_class+0x1228/0x16d0 kernel/locking/lockdep.c:1206
__lock_acquire+0x101/0x6270 kernel/locking/lockdep.c:4259
lock_acquire+0x18b/0x7c0 kernel/locking/lockdep.c:4959
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x32/0x50 kernel/locking/spinlock.c:159
ath9k_htc_rxep+0x31/0x210 drivers/net/wireless/ath/ath9k/htc_drv_txrx.c:1128
ath9k_htc_rx_msg+0x2d9/0xb00 drivers/net/wireless/ath/ath9k/htc_hst.c:459
ath9k_hif_usb_rx_stream drivers/net/wireless/ath/ath9k/hif_usb.c:638 [inline]
ath9k_hif_usb_rx_cb+0xc76/0x1050 drivers/net/wireless/ath/ath9k/hif_usb.c:671
__usb_hcd_giveback_urb+0x29a/0x550 drivers/usb/core/hcd.c:1650
usb_hcd_giveback_urb+0x368/0x420 drivers/usb/core/hcd.c:1716
dummy_timer+0x125e/0x32b4 drivers/usb/gadget/udc/dummy_hcd.c:1967
call_timer_fn+0x1ac/0x6e0 kernel/time/timer.c:1404
expire_timers kernel/time/timer.c:1449 [inline]
__run_timers kernel/time/timer.c:1773 [inline]
__run_timers kernel/time/timer.c:1740 [inline]
run_timer_softirq+0x5e5/0x14c0 kernel/time/timer.c:1786
__do_softirq+0x21e/0x996 kernel/softirq.c:292
asm_call_on_stack+0xf/0x20 arch/x86/entry/entry_64.S:711
</IRQ>
__run_on_irqstack arch/x86/include/asm/irq_stack.h:22 [inline]
run_on_irqstack_cond arch/x86/include/asm/irq_stack.h:48 [inline]
do_softirq_own_stack+0x109/0x140 arch/x86/kernel/irq_64.c:77
invoke_softirq kernel/softirq.c:387 [inline]
__irq_exit_rcu kernel/softirq.c:417 [inline]
irq_exit_rcu+0x16f/0x1a0 kernel/softirq.c:429
sysvec_apic_timer_interrupt+0xd3/0x1b0 arch/x86/kernel/apic/apic.c:1091
asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:596
RIP: 0010:native_irq_disable arch/x86/include/asm/irqflags.h:49 [inline]
RIP: 0010:arch_local_irq_disable arch/x86/include/asm/irqflags.h:89 [inline]
RIP: 0010:acpi_safe_halt drivers/acpi/processor_idle.c:112 [inline]
RIP: 0010:acpi_safe_halt+0x72/0x90 drivers/acpi/processor_idle.c:108
Code: 74 06 5b e9 c0 32 9f fb e8 bb 32 9f fb e8 c6 96 a4 fb e9 0c 00 00 00 e8 ac 32 9f fb 0f 00 2d 45 6e 84 00 e8 a0 32 9f fb fb f4 <fa> e8 b8 94 a4 fb 5b e9 92 32 9f fb 48 89 df e8 7a e1 c8 fb eb ab
RSP: 0018:ffff8881da22fc60 EFLAGS: 00000293
RAX: ffff8881da213200 RBX: 0000000000000000 RCX: 1ffffffff1014efa
RDX: 0000000000000000 RSI: ffffffff85a03aa0 RDI: ffff8881da213a38
RBP: ffff8881d8d2a864 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8881d8d2a864
R13: 1ffff1103b445f96 R14: ffff8881d8d2a865 R15: 0000000000000001
acpi_idle_do_entry+0xa9/0xe0 drivers/acpi/processor_idle.c:525
acpi_idle_enter+0x42b/0xac0 drivers/acpi/processor_idle.c:651
cpuidle_enter_state+0xdb/0xc20 drivers/cpuidle/cpuidle.c:234
cpuidle_enter+0x4a/0xa0 drivers/cpuidle/cpuidle.c:345
call_cpuidle kernel/sched/idle.c:117 [inline]
cpuidle_idle_call kernel/sched/idle.c:207 [inline]
do_idle+0x3c2/0x500 kernel/sched/idle.c:269
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:365
start_secondary+0x294/0x370 arch/x86/kernel/smpboot.c:268
secondary_startup_64+0xb6/0xc0 arch/x86/kernel/head_64.S:243
BUG: unable to handle page fault for address: ffffffffffffffc8
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 7226067 P4D 7226067 PUD 7228067 PMD 0
Oops: 0000 [#1] SMP KASAN
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.8.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:ath9k_htc_rxep+0xb5/0x210 drivers/net/wireless/ath/ath9k/htc_drv_txrx.c:1130
Code: 8b 43 38 48 8d 58 c8 49 39 c4 0f 84 ee 00 00 00 e8 70 56 62 fe 48 89 d8 48 c1 e8 03 0f b6 04 28 84 c0 74 06 0f 8e 0a 01 00 00 <44> 0f b6 3b 31 ff 44 89 fe e8 ad 57 62 fe 45 84 ff 75 a8 e8 43 56
RSP: 0018:ffff8881db3098b0 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffffffffffffffc8 RCX: ffffffff81274370
RDX: 0000000000000000 RSI: ffffffff82dd16d0 RDI: ffff8881db309820
RBP: dffffc0000000000 R08: 0000000000000004 R09: ffffed103b661305
R10: 0000000000000003 R11: ffffed103b661304 R12: ffff8881cd69b538
R13: ffff8881cd69b100 R14: ffff8881cd69b548 R15: ffffed10392ce210
FS: 0000000000000000(0000) GS:ffff8881db300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffc8 CR3: 00000001cf9f6000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
ath9k_htc_rx_msg+0x2d9/0xb00 drivers/net/wireless/ath/ath9k/htc_hst.c:459
ath9k_hif_usb_rx_stream drivers/net/wireless/ath/ath9k/hif_usb.c:638 [inline]
ath9k_hif_usb_rx_cb+0xc76/0x1050 drivers/net/wireless/ath/ath9k/hif_usb.c:671
__usb_hcd_giveback_urb+0x29a/0x550 drivers/usb/core/hcd.c:1650
usb_hcd_giveback_urb+0x368/0x420 drivers/usb/core/hcd.c:1716
dummy_timer+0x125e/0x32b4 drivers/usb/gadget/udc/dummy_hcd.c:1967
call_timer_fn+0x1ac/0x6e0 kernel/time/timer.c:1404
expire_timers kernel/time/timer.c:1449 [inline]
__run_timers kernel/time/timer.c:1773 [inline]
__run_timers kernel/time/timer.c:1740 [inline]
run_timer_softirq+0x5e5/0x14c0 kernel/time/timer.c:1786
__do_softirq+0x21e/0x996 kernel/softirq.c:292
asm_call_on_stack+0xf/0x20 arch/x86/entry/entry_64.S:711
</IRQ>
__run_on_irqstack arch/x86/include/asm/irq_stack.h:22 [inline]
run_on_irqstack_cond arch/x86/include/asm/irq_stack.h:48 [inline]
do_softirq_own_stack+0x109/0x140 arch/x86/kernel/irq_64.c:77
invoke_softirq kernel/softirq.c:387 [inline]
__irq_exit_rcu kernel/softirq.c:417 [inline]
irq_exit_rcu+0x16f/0x1a0 kernel/softirq.c:429
sysvec_apic_timer_interrupt+0xd3/0x1b0 arch/x86/kernel/apic/apic.c:1091
asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:596
RIP: 0010:native_irq_disable arch/x86/include/asm/irqflags.h:49 [inline]
RIP: 0010:arch_local_irq_disable arch/x86/include/asm/irqflags.h:89 [inline]
RIP: 0010:acpi_safe_halt drivers/acpi/processor_idle.c:112 [inline]
RIP: 0010:acpi_safe_halt+0x72/0x90 drivers/acpi/processor_idle.c:108
Code: 74 06 5b e9 c0 32 9f fb e8 bb 32 9f fb e8 c6 96 a4 fb e9 0c 00 00 00 e8 ac 32 9f fb 0f 00 2d 45 6e 84 00 e8 a0 32 9f fb fb f4 <fa> e8 b8 94 a4 fb 5b e9 92 32 9f fb 48 89 df e8 7a e1 c8 fb eb ab
RSP: 0018:ffff8881da22fc60 EFLAGS: 00000293
RAX: ffff8881da213200 RBX: 0000000000000000 RCX: 1ffffffff1014efa
RDX: 0000000000000000 RSI: ffffffff85a03aa0 RDI: ffff8881da213a38
RBP: ffff8881d8d2a864 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8881d8d2a864
R13: 1ffff1103b445f96 R14: ffff8881d8d2a865 R15: 0000000000000001
acpi_idle_do_entry+0xa9/0xe0 drivers/acpi/processor_idle.c:525
acpi_idle_enter+0x42b/0xac0 drivers/acpi/processor_idle.c:651
cpuidle_enter_state+0xdb/0xc20 drivers/cpuidle/cpuidle.c:234
cpuidle_enter+0x4a/0xa0 drivers/cpuidle/cpuidle.c:345
call_cpuidle kernel/sched/idle.c:117 [inline]
cpuidle_idle_call kernel/sched/idle.c:207 [inline]
do_idle+0x3c2/0x500 kernel/sched/idle.c:269
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:365
start_secondary+0x294/0x370 arch/x86/kernel/smpboot.c:268
secondary_startup_64+0xb6/0xc0 arch/x86/kernel/head_64.S:243
Modules linked in:
CR2: ffffffffffffffc8
---[ end trace 5a637b710bbf1999 ]---
RIP: 0010:ath9k_htc_rxep+0xb5/0x210 drivers/net/wireless/ath/ath9k/htc_drv_txrx.c:1130
Code: 8b 43 38 48 8d 58 c8 49 39 c4 0f 84 ee 00 00 00 e8 70 56 62 fe 48 89 d8 48 c1 e8 03 0f b6 04 28 84 c0 74 06 0f 8e 0a 01 00 00 <44> 0f b6 3b 31 ff 44 89 fe e8 ad 57 62 fe 45 84 ff 75 a8 e8 43 56
RSP: 0018:ffff8881db3098b0 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffffffffffffffc8 RCX: ffffffff81274370
RDX: 0000000000000000 RSI: ffffffff82dd16d0 RDI: ffff8881db309820
RBP: dffffc0000000000 R08: 0000000000000004 R09: ffffed103b661305
R10: 0000000000000003 R11: ffffed103b661304 R12: ffff8881cd69b538
R13: ffff8881cd69b100 R14: ffff8881cd69b548 R15: ffffed10392ce210
FS: 0000000000000000(0000) GS:ffff8881db300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffc8 CR3: 00000001cf9f6000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: INFO: trying to register non-static key in ath9k_htc_rxep
2020-09-23 18:28 ` Brooke Basile
@ 2020-09-23 18:32 ` Andrey Konovalov
0 siblings, 0 replies; 9+ messages in thread
From: Andrey Konovalov @ 2020-09-23 18:32 UTC (permalink / raw)
To: Brooke Basile
Cc: Dmitry Vyukov, Greg Kroah-Hartman, syzbot, syzkaller-bugs,
USB list, linux-kernel-mentees
On Wed, Sep 23, 2020 at 8:28 PM Brooke Basile <brookebasile@gmail.com> wrote:
>
> On 9/23/20 2:06 PM, Andrey Konovalov wrote:
> > On Wed, Sep 23, 2020 at 7:42 PM Brooke Basile <brookebasile@gmail.com> wrote:
> >>
> >> On 9/22/20 3:38 AM, Dmitry Vyukov wrote:
> >>> On Tue, Sep 22, 2020 at 9:26 AM Greg Kroah-Hartman
> >>> <gregkh@linuxfoundation.org> wrote:
> >>>>
> >>>> On Tue, Sep 22, 2020 at 08:49:39AM +0200, Dmitry Vyukov wrote:
> >>>>> On Tue, Sep 22, 2020 at 8:21 AM syzbot
> >>>>> <syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com> wrote:
> >>>>>>
> >>>>>> Hello,
> >>>>>>
> >>>>>> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
> >>>>>>
> >>>>>> Reported-and-tested-by: syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com
> >>>>>>
> >>>>>> Tested on:
> >>>>>>
> >>>>>> commit: 98477740 Merge branch 'rcu/urgent' of git://git.kernel.org..
> >>>>>> git tree: upstream
> >>>>>> kernel config: https://syzkaller.appspot.com/x/.config?x=2c523334171d074
> >>>>>> dashboard link: https://syzkaller.appspot.com/bug?extid=4d2d56175b934b9a7bf9
> >>>>>> compiler: gcc (GCC) 10.1.0-syz 20200507
> >>>>>>
> >>>>>> Note: testing is done by a robot and is best-effort only.
> >>>>>
> >>>>> Hi Brooke,
> >>>>>
> >>>>> As far as I understand, UBS is currently completely broken on upstream
> >>>>> HEAD, so testing any USB bugs on upstream HEAD will lead to false
> >>>>> positive results only.
> >>>>
> >>>> Broken in what way? I don't see any bug reports here...
> >>>
> >>> I mean this "USB driver ID matching broke":
> >>> https://groups.google.com/g/syzkaller/c/VKfxh__m05w/m/ArzTtar-AgAJ
> >>> syzkaller can't test usb, nor reproduce any existing bugs on the upstream tree.
> >>>
> >>
> >> Hi Dmitry,
> >>
> >> Thanks for the heads up and for the link to the thread with the information.
> >>
> >> I recently fixed the following bug:
> >> https://syzkaller.appspot.com/bug?id=cabffad18eb74197f84871802fd2c5117b61febf
> >>
> >> I tested this on my local syzkaller instance before sending it in to
> >> syzbot and the kernel panic was resolved, however I did get "-busid- is
> >> not in match_busid table... skip!" in dmesg-- should this be taken as a
> >> false positive as well?
> >
> > Hi Brooke,
> >
> > Yes, this line means that the kernel is broken and testing USB
> > programs with syzkaller is impossible.
> >
> > Thanks!
> >
> Gotcha, I'll hold off on working on USB bugs for now then.
>
> The above patch has already been applied to the ath-next tree:
> https://patchwork.kernel.org/patch/11769845/
>
> Should I have the patch reverted or is it safe to assume that any
> regressions will be caught in the -next tree?
If you believe the patch fixes the issue, then it makes sense to keep
it. If it actually doesn't, syzbot will report the bug again once the
patch is in the mainline.
Thanks!
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: INFO: trying to register non-static key in ath9k_htc_rxep
2020-09-23 18:06 ` Andrey Konovalov
@ 2020-09-23 18:28 ` Brooke Basile
2020-09-23 18:32 ` Andrey Konovalov
0 siblings, 1 reply; 9+ messages in thread
From: Brooke Basile @ 2020-09-23 18:28 UTC (permalink / raw)
To: Andrey Konovalov
Cc: Dmitry Vyukov, Greg Kroah-Hartman, syzbot, syzkaller-bugs,
USB list, linux-kernel-mentees
On 9/23/20 2:06 PM, Andrey Konovalov wrote:
> On Wed, Sep 23, 2020 at 7:42 PM Brooke Basile <brookebasile@gmail.com> wrote:
>>
>> On 9/22/20 3:38 AM, Dmitry Vyukov wrote:
>>> On Tue, Sep 22, 2020 at 9:26 AM Greg Kroah-Hartman
>>> <gregkh@linuxfoundation.org> wrote:
>>>>
>>>> On Tue, Sep 22, 2020 at 08:49:39AM +0200, Dmitry Vyukov wrote:
>>>>> On Tue, Sep 22, 2020 at 8:21 AM syzbot
>>>>> <syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com> wrote:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>>>>>>
>>>>>> Reported-and-tested-by: syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com
>>>>>>
>>>>>> Tested on:
>>>>>>
>>>>>> commit: 98477740 Merge branch 'rcu/urgent' of git://git.kernel.org..
>>>>>> git tree: upstream
>>>>>> kernel config: https://syzkaller.appspot.com/x/.config?x=2c523334171d074
>>>>>> dashboard link: https://syzkaller.appspot.com/bug?extid=4d2d56175b934b9a7bf9
>>>>>> compiler: gcc (GCC) 10.1.0-syz 20200507
>>>>>>
>>>>>> Note: testing is done by a robot and is best-effort only.
>>>>>
>>>>> Hi Brooke,
>>>>>
>>>>> As far as I understand, UBS is currently completely broken on upstream
>>>>> HEAD, so testing any USB bugs on upstream HEAD will lead to false
>>>>> positive results only.
>>>>
>>>> Broken in what way? I don't see any bug reports here...
>>>
>>> I mean this "USB driver ID matching broke":
>>> https://groups.google.com/g/syzkaller/c/VKfxh__m05w/m/ArzTtar-AgAJ
>>> syzkaller can't test usb, nor reproduce any existing bugs on the upstream tree.
>>>
>>
>> Hi Dmitry,
>>
>> Thanks for the heads up and for the link to the thread with the information.
>>
>> I recently fixed the following bug:
>> https://syzkaller.appspot.com/bug?id=cabffad18eb74197f84871802fd2c5117b61febf
>>
>> I tested this on my local syzkaller instance before sending it in to
>> syzbot and the kernel panic was resolved, however I did get "-busid- is
>> not in match_busid table... skip!" in dmesg-- should this be taken as a
>> false positive as well?
>
> Hi Brooke,
>
> Yes, this line means that the kernel is broken and testing USB
> programs with syzkaller is impossible.
>
> Thanks!
>
Gotcha, I'll hold off on working on USB bugs for now then.
The above patch has already been applied to the ath-next tree:
https://patchwork.kernel.org/patch/11769845/
Should I have the patch reverted or is it safe to assume that any
regressions will be caught in the -next tree?
Thank you,
Brooke Basile
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: INFO: trying to register non-static key in ath9k_htc_rxep
2020-09-23 17:42 ` Brooke Basile
@ 2020-09-23 18:06 ` Andrey Konovalov
2020-09-23 18:28 ` Brooke Basile
0 siblings, 1 reply; 9+ messages in thread
From: Andrey Konovalov @ 2020-09-23 18:06 UTC (permalink / raw)
To: Brooke Basile
Cc: Dmitry Vyukov, Greg Kroah-Hartman, syzbot, syzkaller-bugs,
USB list, linux-kernel-mentees
On Wed, Sep 23, 2020 at 7:42 PM Brooke Basile <brookebasile@gmail.com> wrote:
>
> On 9/22/20 3:38 AM, Dmitry Vyukov wrote:
> > On Tue, Sep 22, 2020 at 9:26 AM Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> >>
> >> On Tue, Sep 22, 2020 at 08:49:39AM +0200, Dmitry Vyukov wrote:
> >>> On Tue, Sep 22, 2020 at 8:21 AM syzbot
> >>> <syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com> wrote:
> >>>>
> >>>> Hello,
> >>>>
> >>>> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
> >>>>
> >>>> Reported-and-tested-by: syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com
> >>>>
> >>>> Tested on:
> >>>>
> >>>> commit: 98477740 Merge branch 'rcu/urgent' of git://git.kernel.org..
> >>>> git tree: upstream
> >>>> kernel config: https://syzkaller.appspot.com/x/.config?x=2c523334171d074
> >>>> dashboard link: https://syzkaller.appspot.com/bug?extid=4d2d56175b934b9a7bf9
> >>>> compiler: gcc (GCC) 10.1.0-syz 20200507
> >>>>
> >>>> Note: testing is done by a robot and is best-effort only.
> >>>
> >>> Hi Brooke,
> >>>
> >>> As far as I understand, UBS is currently completely broken on upstream
> >>> HEAD, so testing any USB bugs on upstream HEAD will lead to false
> >>> positive results only.
> >>
> >> Broken in what way? I don't see any bug reports here...
> >
> > I mean this "USB driver ID matching broke":
> > https://groups.google.com/g/syzkaller/c/VKfxh__m05w/m/ArzTtar-AgAJ
> > syzkaller can't test usb, nor reproduce any existing bugs on the upstream tree.
> >
>
> Hi Dmitry,
>
> Thanks for the heads up and for the link to the thread with the information.
>
> I recently fixed the following bug:
> https://syzkaller.appspot.com/bug?id=cabffad18eb74197f84871802fd2c5117b61febf
>
> I tested this on my local syzkaller instance before sending it in to
> syzbot and the kernel panic was resolved, however I did get "-busid- is
> not in match_busid table... skip!" in dmesg-- should this be taken as a
> false positive as well?
Hi Brooke,
Yes, this line means that the kernel is broken and testing USB
programs with syzkaller is impossible.
Thanks!
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: INFO: trying to register non-static key in ath9k_htc_rxep
2020-09-22 7:38 ` Dmitry Vyukov
@ 2020-09-23 17:42 ` Brooke Basile
2020-09-23 18:06 ` Andrey Konovalov
0 siblings, 1 reply; 9+ messages in thread
From: Brooke Basile @ 2020-09-23 17:42 UTC (permalink / raw)
To: Dmitry Vyukov, Greg Kroah-Hartman
Cc: syzbot, syzkaller-bugs, Andrey Konovalov, USB list, linux-kernel-mentees
On 9/22/20 3:38 AM, Dmitry Vyukov wrote:
> On Tue, Sep 22, 2020 at 9:26 AM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>>
>> On Tue, Sep 22, 2020 at 08:49:39AM +0200, Dmitry Vyukov wrote:
>>> On Tue, Sep 22, 2020 at 8:21 AM syzbot
>>> <syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com> wrote:
>>>>
>>>> Hello,
>>>>
>>>> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>>>>
>>>> Reported-and-tested-by: syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com
>>>>
>>>> Tested on:
>>>>
>>>> commit: 98477740 Merge branch 'rcu/urgent' of git://git.kernel.org..
>>>> git tree: upstream
>>>> kernel config: https://syzkaller.appspot.com/x/.config?x=2c523334171d074
>>>> dashboard link: https://syzkaller.appspot.com/bug?extid=4d2d56175b934b9a7bf9
>>>> compiler: gcc (GCC) 10.1.0-syz 20200507
>>>>
>>>> Note: testing is done by a robot and is best-effort only.
>>>
>>> Hi Brooke,
>>>
>>> As far as I understand, UBS is currently completely broken on upstream
>>> HEAD, so testing any USB bugs on upstream HEAD will lead to false
>>> positive results only.
>>
>> Broken in what way? I don't see any bug reports here...
>
> I mean this "USB driver ID matching broke":
> https://groups.google.com/g/syzkaller/c/VKfxh__m05w/m/ArzTtar-AgAJ
> syzkaller can't test usb, nor reproduce any existing bugs on the upstream tree.
>
Hi Dmitry,
Thanks for the heads up and for the link to the thread with the information.
I recently fixed the following bug:
https://syzkaller.appspot.com/bug?id=cabffad18eb74197f84871802fd2c5117b61febf
I tested this on my local syzkaller instance before sending it in to
syzbot and the kernel panic was resolved, however I did get "-busid- is
not in match_busid table... skip!" in dmesg-- should this be taken as a
false positive as well?
Best,
Brooke Basile
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: INFO: trying to register non-static key in ath9k_htc_rxep
2020-09-22 7:26 ` Greg Kroah-Hartman
@ 2020-09-22 7:38 ` Dmitry Vyukov
2020-09-23 17:42 ` Brooke Basile
0 siblings, 1 reply; 9+ messages in thread
From: Dmitry Vyukov @ 2020-09-22 7:38 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: syzbot, Brooke Basile, syzkaller-bugs, Andrey Konovalov,
USB list, linux-kernel-mentees
On Tue, Sep 22, 2020 at 9:26 AM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Tue, Sep 22, 2020 at 08:49:39AM +0200, Dmitry Vyukov wrote:
> > On Tue, Sep 22, 2020 at 8:21 AM syzbot
> > <syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com> wrote:
> > >
> > > Hello,
> > >
> > > syzbot has tested the proposed patch and the reproducer did not trigger any issue:
> > >
> > > Reported-and-tested-by: syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com
> > >
> > > Tested on:
> > >
> > > commit: 98477740 Merge branch 'rcu/urgent' of git://git.kernel.org..
> > > git tree: upstream
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=2c523334171d074
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=4d2d56175b934b9a7bf9
> > > compiler: gcc (GCC) 10.1.0-syz 20200507
> > >
> > > Note: testing is done by a robot and is best-effort only.
> >
> > Hi Brooke,
> >
> > As far as I understand, UBS is currently completely broken on upstream
> > HEAD, so testing any USB bugs on upstream HEAD will lead to false
> > positive results only.
>
> Broken in what way? I don't see any bug reports here...
I mean this "USB driver ID matching broke":
https://groups.google.com/g/syzkaller/c/VKfxh__m05w/m/ArzTtar-AgAJ
syzkaller can't test usb, nor reproduce any existing bugs on the upstream tree.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: INFO: trying to register non-static key in ath9k_htc_rxep
2020-09-22 6:49 ` Dmitry Vyukov
@ 2020-09-22 7:26 ` Greg Kroah-Hartman
2020-09-22 7:38 ` Dmitry Vyukov
0 siblings, 1 reply; 9+ messages in thread
From: Greg Kroah-Hartman @ 2020-09-22 7:26 UTC (permalink / raw)
To: Dmitry Vyukov
Cc: syzbot, Brooke Basile, syzkaller-bugs, Andrey Konovalov,
USB list, linux-kernel-mentees
On Tue, Sep 22, 2020 at 08:49:39AM +0200, Dmitry Vyukov wrote:
> On Tue, Sep 22, 2020 at 8:21 AM syzbot
> <syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com> wrote:
> >
> > Hello,
> >
> > syzbot has tested the proposed patch and the reproducer did not trigger any issue:
> >
> > Reported-and-tested-by: syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com
> >
> > Tested on:
> >
> > commit: 98477740 Merge branch 'rcu/urgent' of git://git.kernel.org..
> > git tree: upstream
> > kernel config: https://syzkaller.appspot.com/x/.config?x=2c523334171d074
> > dashboard link: https://syzkaller.appspot.com/bug?extid=4d2d56175b934b9a7bf9
> > compiler: gcc (GCC) 10.1.0-syz 20200507
> >
> > Note: testing is done by a robot and is best-effort only.
>
> Hi Brooke,
>
> As far as I understand, UBS is currently completely broken on upstream
> HEAD, so testing any USB bugs on upstream HEAD will lead to false
> positive results only.
Broken in what way? I don't see any bug reports here...
thanks,
greg k-h
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: INFO: trying to register non-static key in ath9k_htc_rxep
[not found] ` <000000000000cce55c05afe0f8f0@google.com>
@ 2020-09-22 6:49 ` Dmitry Vyukov
2020-09-22 7:26 ` Greg Kroah-Hartman
0 siblings, 1 reply; 9+ messages in thread
From: Dmitry Vyukov @ 2020-09-22 6:49 UTC (permalink / raw)
To: syzbot
Cc: Brooke Basile, syzkaller-bugs, Andrey Konovalov, USB list,
Greg Kroah-Hartman, linux-kernel-mentees
On Tue, Sep 22, 2020 at 8:21 AM syzbot
<syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>
> Reported-and-tested-by: syzbot+4d2d56175b934b9a7bf9@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: 98477740 Merge branch 'rcu/urgent' of git://git.kernel.org..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=2c523334171d074
> dashboard link: https://syzkaller.appspot.com/bug?extid=4d2d56175b934b9a7bf9
> compiler: gcc (GCC) 10.1.0-syz 20200507
>
> Note: testing is done by a robot and is best-effort only.
Hi Brooke,
As far as I understand, UBS is currently completely broken on upstream
HEAD, so testing any USB bugs on upstream HEAD will lead to false
positive results only.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2020-09-23 18:32 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-18 20:57 INFO: trying to register non-static key in ath9k_htc_rxep syzbot
2020-06-20 10:57 ` syzbot
[not found] <13659a4e-ad71-0cef-4bfa-3eb4b8c73f4b@gmail.com>
[not found] ` <000000000000cce55c05afe0f8f0@google.com>
2020-09-22 6:49 ` Dmitry Vyukov
2020-09-22 7:26 ` Greg Kroah-Hartman
2020-09-22 7:38 ` Dmitry Vyukov
2020-09-23 17:42 ` Brooke Basile
2020-09-23 18:06 ` Andrey Konovalov
2020-09-23 18:28 ` Brooke Basile
2020-09-23 18:32 ` Andrey Konovalov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).