KASAN: stack-out-of-bounds Read in refcount_inc_not_zero_checked
12 views
Skip to first unread message
syzbot
Nov 14, 2018, 2:18:08 AM11/14/18
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 3e536cff3424 net: phy: check if advertising is zero using ..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=178a0893400000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a0a89f12ca9b0f5
dashboard link: https://syzkaller.appspot.com/bug?extid=e68cece14ddc29e2694d
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [crec...@redhat.com kees...@chromium.org
linux-...@vger.kernel.org linu...@kvack.org]
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+e68cec...@syzkaller.appspotmail.com
cannot load conntrack support for proto=7
==================================================================
kasan: CONFIG_KASAN_INLINE enabled
BUG: KASAN: stack-out-of-bounds in atomic_read
include/asm-generic/atomic-instrumented.h:21 [inline]
BUG: KASAN: stack-out-of-bounds in refcount_inc_not_zero_checked+0x97/0x2f0
lib/refcount.c:120
kasan: GPF could be caused by NULL-ptr deref or user memory access
Read of size 4 at addr ffff8881da9c0bf0 by task kworker/u4:1/21
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 8057 Comm: syz-executor4 Not tainted 4.20.0-rc2+ #294
CPU: 1 PID: 21 Comm: kworker/u4:1 Not tainted 4.20.0-rc2+ #294
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:lookup_object lib/debugobjects.c:157 [inline]
RIP: 0010:debug_object_deactivate+0x191/0x450 lib/debugobjects.c:543
Workqueue: call_usermodehelper_exec_work (events_unbound)
------------[ cut here ]------------
Call Trace:
Bad or missing usercopy whitelist? Kernel memory overwrite attempt detected
to SLAB object '$' (offset 224, size 64)!
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x244/0x39d lib/dump_stack.c:113
WARNING: CPU: 0 PID: 8057 at mm/usercopy.c:83 usercopy_warn+0xee/0x110
mm/usercopy.c:78
Kernel panic - not syncing: panic_on_warn set ...
print_address_description.cold.7+0x9/0x1ff mm/kasan/report.c:256
kasan_report_error mm/kasan/report.c:354 [inline]
kasan_report.cold.8+0x242/0x309 mm/kasan/report.c:412
check_memory_region_inline mm/kasan/kasan.c:260 [inline]
check_memory_region+0x13e/0x1b0 mm/kasan/kasan.c:267
kasan_check_read+0x11/0x20 mm/kasan/kasan.c:272
atomic_read include/asm-generic/atomic-instrumented.h:21 [inline]
refcount_inc_not_zero_checked+0x97/0x2f0 lib/refcount.c:120
refcount_inc_checked+0x15/0x70 lib/refcount.c:153
kref_get include/linux/kref.h:47 [inline]
aa_get_label security/apparmor/include/label.h:387 [inline]
aa_get_newest_label security/apparmor/include/label.h:441 [inline]
apparmor_cred_prepare+0x307/0x5a0 security/apparmor/lsm.c:80
security_prepare_creds+0x60/0xc0 security/security.c:1022
prepare_creds+0x3b9/0x4d0 kernel/cred.c:278
copy_creds+0x79/0x560 kernel/cred.c:344
copy_process+0x1266/0x87a0 kernel/fork.c:1784
_do_fork+0x1cb/0x11d0 kernel/fork.c:2216
kernel_thread+0x34/0x40 kernel/fork.c:2275
call_usermodehelper_exec_sync kernel/umh.c:130 [inline]
call_usermodehelper_exec_work+0xc9/0x2f0 kernel/umh.c:182
process_one_work+0xc90/0x1c40 kernel/workqueue.c:2153
worker_thread+0x17f/0x1390 kernel/workqueue.c:2296
kthread+0x35a/0x440 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
The buggy address belongs to the object at ffff8881da9c0040
which belongs to the cache of size -30591
The buggy address is located 33583 bytes to the right of
-30591-byte region [ffff8881da9c0040, ffff8881da9b88c1)
The buggy address belongs to the page:
page:ffffea00076a7000 count:1 mapcount:0 mapping:ffff8881da800ac0 index:0x0
compound_mapcount: 0
flags: 0x2fffc0000010200(slab|head)
raw: 02fffc0000010200 ffffea00076a4108 ffffea0007650a08 ffff8881da800ac0
raw: 0000000000000000 ffff8881da9c0040 0000000100000007 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8881da9c0a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1
ffff8881da9c0b00: f1 00 f2 f2 f2 f2 f2 f2 f2 f8 f2 f2 f2 00 00 00
> ffff8881da9c0b80: 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1
^
ffff8881da9c0c00: f1 f8 f2 f2 f2 00 00 00 00 00 00 00 00 00 00 00
ffff8881da9c0c80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc 00
==================================================================
Kernel Offset: disabled
======================================================
WARNING: possible circular locking dependency detected
4.20.0-rc2+ #294 Not tainted
------------------------------------------------------
syz-executor4/8057 is trying to acquire lock:
0000000019252f0a ((console_sem).lock){-.-.}, at: down_trylock+0x13/0x70
kernel/locking/semaphore.c:136
but task is already holding lock:
000000003a11d92b (&obj_hash[i].lock){-.-.}, at:
debug_object_deactivate+0xf7/0x450 lib/debugobjects.c:541
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #3 (&obj_hash[i].lock){-.-.}:
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x99/0xd0 kernel/locking/spinlock.c:152
__debug_object_init+0x127/0x1290 lib/debugobjects.c:384
debug_object_init+0x16/0x20 lib/debugobjects.c:432
debug_hrtimer_init kernel/time/hrtimer.c:410 [inline]
debug_init kernel/time/hrtimer.c:458 [inline]
hrtimer_init+0x97/0x490 kernel/time/hrtimer.c:1308
init_dl_task_timer+0x1b/0x50 kernel/sched/deadline.c:1057
__sched_fork+0x2ae/0x590 kernel/sched/core.c:2166
init_idle+0x75/0x740 kernel/sched/core.c:5374
sched_init+0xb33/0xc07 kernel/sched/core.c:6060
start_kernel+0x4be/0xa2b init/main.c:608
x86_64_start_reservations+0x2e/0x30 arch/x86/kernel/head64.c:472
x86_64_start_kernel+0x76/0x79 arch/x86/kernel/head64.c:451
secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:243
-> #2 (&rq->lock){-.-.}:
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2d/0x40 kernel/locking/spinlock.c:144
rq_lock kernel/sched/sched.h:1126 [inline]
task_fork_fair+0xb0/0x6d0 kernel/sched/fair.c:9768
sched_fork+0x443/0xba0 kernel/sched/core.c:2359
copy_process+0x25b8/0x87a0 kernel/fork.c:1887
_do_fork+0x1cb/0x11d0 kernel/fork.c:2216
kernel_thread+0x34/0x40 kernel/fork.c:2275
rest_init+0x28/0x372 init/main.c:409
arch_call_rest_init+0xe/0x1b
start_kernel+0x9f0/0xa2b init/main.c:745
x86_64_start_reservations+0x2e/0x30 arch/x86/kernel/head64.c:472
x86_64_start_kernel+0x76/0x79 arch/x86/kernel/head64.c:451
secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:243
-> #1 (&p->pi_lock){-.-.}:
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x99/0xd0 kernel/locking/spinlock.c:152
try_to_wake_up+0xdc/0x1490 kernel/sched/core.c:1965
wake_up_process+0x10/0x20 kernel/sched/core.c:2129
__up.isra.1+0x1c0/0x2a0 kernel/locking/semaphore.c:262
up+0x13c/0x1c0 kernel/locking/semaphore.c:187
__up_console_sem+0xbe/0x1b0 kernel/printk/printk.c:236
console_unlock+0x811/0x1190 kernel/printk/printk.c:2432
vprintk_emit+0x391/0x990 kernel/printk/printk.c:1922
vprintk_default+0x28/0x30 kernel/printk/printk.c:1964
vprintk_func+0x7e/0x181 kernel/printk/printk_safe.c:398
printk+0xa7/0xcf kernel/printk/printk.c:1997
kobject_uevent_env+0x96/0x101e lib/kobject_uevent.c:467
call_crda net/wireless/reg.c:556 [inline]
reg_query_database+0x283/0x400 net/wireless/reg.c:1104
reg_process_hint_core net/wireless/reg.c:2339 [inline]
reg_process_hint+0x189/0xec0 net/wireless/reg.c:2677
reg_process_pending_hints net/wireless/reg.c:2767 [inline]
reg_todo+0x49a/0xc20 net/wireless/reg.c:2844
process_one_work+0xc90/0x1c40 kernel/workqueue.c:2153
worker_thread+0x17f/0x1390 kernel/workqueue.c:2296
kthread+0x35a/0x440 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
-> #0 ((console_sem).lock){-.-.}:
other info that might help us debug this:
Chain exists of:
(console_sem).lock --> &rq->lock --> &obj_hash[i].lock
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&obj_hash[i].lock);
lock(&rq->lock);
lock(&obj_hash[i].lock);
lock((console_sem).lock);
*** DEADLOCK ***
5 locks held by syz-executor4/8057:
#0: 000000001cf43636 (rcu_read_lock){....}, at: __skb_unlink
include/linux/skbuff.h:1893 [inline]
#0: 000000001cf43636 (rcu_read_lock){....}, at: __skb_dequeue
include/linux/skbuff.h:1909 [inline]
#0: 000000001cf43636 (rcu_read_lock){....}, at:
process_backlog+0x1dd/0x7a0 net/core/dev.c:5855
#1: 000000001cf43636 (rcu_read_lock){....}, at: __skb_pull
include/linux/skbuff.h:2126 [inline]
#1: 000000001cf43636 (rcu_read_lock){....}, at:
ip_local_deliver_finish+0x13d/0x390 net/ipv4/ip_input.c:231
#2: 000000005ccb0f38 (hrtimer_bases.lock){-.-.}, at:
hrtimer_interrupt+0xfc/0x780 kernel/time/hrtimer.c:1499
#3: 000000003a11d92b (&obj_hash[i].lock){-.-.}, at:
debug_object_deactivate+0xf7/0x450 lib/debugobjects.c:541
#4: 000000001cf43636 (rcu_read_lock){....}, at:
atomic_notifier_call_chain+0x0/0x190 kernel/notifier.c:329
stack backtrace:
CPU: 0 PID: 8057 Comm: syz-executor4 Not tainted 4.20.0-rc2+ #294
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
Rebooting in 86400 seconds..
---
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 syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
syzbot found the following crash on:
HEAD commit: 3e536cff3424 net: phy: check if advertising is zero using ..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=178a0893400000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a0a89f12ca9b0f5
dashboard link: https://syzkaller.appspot.com/bug?extid=e68cece14ddc29e2694d
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [crec...@redhat.com kees...@chromium.org
linux-...@vger.kernel.org linu...@kvack.org]
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+e68cec...@syzkaller.appspotmail.com
cannot load conntrack support for proto=7
==================================================================
kasan: CONFIG_KASAN_INLINE enabled
BUG: KASAN: stack-out-of-bounds in atomic_read
include/asm-generic/atomic-instrumented.h:21 [inline]
BUG: KASAN: stack-out-of-bounds in refcount_inc_not_zero_checked+0x97/0x2f0
lib/refcount.c:120
kasan: GPF could be caused by NULL-ptr deref or user memory access
Read of size 4 at addr ffff8881da9c0bf0 by task kworker/u4:1/21
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 8057 Comm: syz-executor4 Not tainted 4.20.0-rc2+ #294
CPU: 1 PID: 21 Comm: kworker/u4:1 Not tainted 4.20.0-rc2+ #294
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:lookup_object lib/debugobjects.c:157 [inline]
RIP: 0010:debug_object_deactivate+0x191/0x450 lib/debugobjects.c:543
Workqueue: call_usermodehelper_exec_work (events_unbound)
------------[ cut here ]------------
Call Trace:
Bad or missing usercopy whitelist? Kernel memory overwrite attempt detected
to SLAB object '$' (offset 224, size 64)!
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x244/0x39d lib/dump_stack.c:113
WARNING: CPU: 0 PID: 8057 at mm/usercopy.c:83 usercopy_warn+0xee/0x110
mm/usercopy.c:78
Kernel panic - not syncing: panic_on_warn set ...
print_address_description.cold.7+0x9/0x1ff mm/kasan/report.c:256
kasan_report_error mm/kasan/report.c:354 [inline]
kasan_report.cold.8+0x242/0x309 mm/kasan/report.c:412
check_memory_region_inline mm/kasan/kasan.c:260 [inline]
check_memory_region+0x13e/0x1b0 mm/kasan/kasan.c:267
kasan_check_read+0x11/0x20 mm/kasan/kasan.c:272
atomic_read include/asm-generic/atomic-instrumented.h:21 [inline]
refcount_inc_not_zero_checked+0x97/0x2f0 lib/refcount.c:120
refcount_inc_checked+0x15/0x70 lib/refcount.c:153
kref_get include/linux/kref.h:47 [inline]
aa_get_label security/apparmor/include/label.h:387 [inline]
aa_get_newest_label security/apparmor/include/label.h:441 [inline]
apparmor_cred_prepare+0x307/0x5a0 security/apparmor/lsm.c:80
security_prepare_creds+0x60/0xc0 security/security.c:1022
prepare_creds+0x3b9/0x4d0 kernel/cred.c:278
copy_creds+0x79/0x560 kernel/cred.c:344
copy_process+0x1266/0x87a0 kernel/fork.c:1784
_do_fork+0x1cb/0x11d0 kernel/fork.c:2216
kernel_thread+0x34/0x40 kernel/fork.c:2275
call_usermodehelper_exec_sync kernel/umh.c:130 [inline]
call_usermodehelper_exec_work+0xc9/0x2f0 kernel/umh.c:182
process_one_work+0xc90/0x1c40 kernel/workqueue.c:2153
worker_thread+0x17f/0x1390 kernel/workqueue.c:2296
kthread+0x35a/0x440 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
The buggy address belongs to the object at ffff8881da9c0040
which belongs to the cache of size -30591
The buggy address is located 33583 bytes to the right of
-30591-byte region [ffff8881da9c0040, ffff8881da9b88c1)
The buggy address belongs to the page:
page:ffffea00076a7000 count:1 mapcount:0 mapping:ffff8881da800ac0 index:0x0
compound_mapcount: 0
flags: 0x2fffc0000010200(slab|head)
raw: 02fffc0000010200 ffffea00076a4108 ffffea0007650a08 ffff8881da800ac0
raw: 0000000000000000 ffff8881da9c0040 0000000100000007 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8881da9c0a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1
ffff8881da9c0b00: f1 00 f2 f2 f2 f2 f2 f2 f2 f8 f2 f2 f2 00 00 00
> ffff8881da9c0b80: 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1
^
ffff8881da9c0c00: f1 f8 f2 f2 f2 00 00 00 00 00 00 00 00 00 00 00
ffff8881da9c0c80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc 00
==================================================================
Kernel Offset: disabled
======================================================
WARNING: possible circular locking dependency detected
4.20.0-rc2+ #294 Not tainted
------------------------------------------------------
syz-executor4/8057 is trying to acquire lock:
0000000019252f0a ((console_sem).lock){-.-.}, at: down_trylock+0x13/0x70
kernel/locking/semaphore.c:136
but task is already holding lock:
000000003a11d92b (&obj_hash[i].lock){-.-.}, at:
debug_object_deactivate+0xf7/0x450 lib/debugobjects.c:541
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #3 (&obj_hash[i].lock){-.-.}:
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x99/0xd0 kernel/locking/spinlock.c:152
__debug_object_init+0x127/0x1290 lib/debugobjects.c:384
debug_object_init+0x16/0x20 lib/debugobjects.c:432
debug_hrtimer_init kernel/time/hrtimer.c:410 [inline]
debug_init kernel/time/hrtimer.c:458 [inline]
hrtimer_init+0x97/0x490 kernel/time/hrtimer.c:1308
init_dl_task_timer+0x1b/0x50 kernel/sched/deadline.c:1057
__sched_fork+0x2ae/0x590 kernel/sched/core.c:2166
init_idle+0x75/0x740 kernel/sched/core.c:5374
sched_init+0xb33/0xc07 kernel/sched/core.c:6060
start_kernel+0x4be/0xa2b init/main.c:608
x86_64_start_reservations+0x2e/0x30 arch/x86/kernel/head64.c:472
x86_64_start_kernel+0x76/0x79 arch/x86/kernel/head64.c:451
secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:243
-> #2 (&rq->lock){-.-.}:
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2d/0x40 kernel/locking/spinlock.c:144
rq_lock kernel/sched/sched.h:1126 [inline]
task_fork_fair+0xb0/0x6d0 kernel/sched/fair.c:9768
sched_fork+0x443/0xba0 kernel/sched/core.c:2359
copy_process+0x25b8/0x87a0 kernel/fork.c:1887
_do_fork+0x1cb/0x11d0 kernel/fork.c:2216
kernel_thread+0x34/0x40 kernel/fork.c:2275
rest_init+0x28/0x372 init/main.c:409
arch_call_rest_init+0xe/0x1b
start_kernel+0x9f0/0xa2b init/main.c:745
x86_64_start_reservations+0x2e/0x30 arch/x86/kernel/head64.c:472
x86_64_start_kernel+0x76/0x79 arch/x86/kernel/head64.c:451
secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:243
-> #1 (&p->pi_lock){-.-.}:
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x99/0xd0 kernel/locking/spinlock.c:152
try_to_wake_up+0xdc/0x1490 kernel/sched/core.c:1965
wake_up_process+0x10/0x20 kernel/sched/core.c:2129
__up.isra.1+0x1c0/0x2a0 kernel/locking/semaphore.c:262
up+0x13c/0x1c0 kernel/locking/semaphore.c:187
__up_console_sem+0xbe/0x1b0 kernel/printk/printk.c:236
console_unlock+0x811/0x1190 kernel/printk/printk.c:2432
vprintk_emit+0x391/0x990 kernel/printk/printk.c:1922
vprintk_default+0x28/0x30 kernel/printk/printk.c:1964
vprintk_func+0x7e/0x181 kernel/printk/printk_safe.c:398
printk+0xa7/0xcf kernel/printk/printk.c:1997
kobject_uevent_env+0x96/0x101e lib/kobject_uevent.c:467
call_crda net/wireless/reg.c:556 [inline]
reg_query_database+0x283/0x400 net/wireless/reg.c:1104
reg_process_hint_core net/wireless/reg.c:2339 [inline]
reg_process_hint+0x189/0xec0 net/wireless/reg.c:2677
reg_process_pending_hints net/wireless/reg.c:2767 [inline]
reg_todo+0x49a/0xc20 net/wireless/reg.c:2844
process_one_work+0xc90/0x1c40 kernel/workqueue.c:2153
worker_thread+0x17f/0x1390 kernel/workqueue.c:2296
kthread+0x35a/0x440 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
-> #0 ((console_sem).lock){-.-.}:
other info that might help us debug this:
Chain exists of:
(console_sem).lock --> &rq->lock --> &obj_hash[i].lock
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&obj_hash[i].lock);
lock(&rq->lock);
lock(&obj_hash[i].lock);
lock((console_sem).lock);
*** DEADLOCK ***
5 locks held by syz-executor4/8057:
#0: 000000001cf43636 (rcu_read_lock){....}, at: __skb_unlink
include/linux/skbuff.h:1893 [inline]
#0: 000000001cf43636 (rcu_read_lock){....}, at: __skb_dequeue
include/linux/skbuff.h:1909 [inline]
#0: 000000001cf43636 (rcu_read_lock){....}, at:
process_backlog+0x1dd/0x7a0 net/core/dev.c:5855
#1: 000000001cf43636 (rcu_read_lock){....}, at: __skb_pull
include/linux/skbuff.h:2126 [inline]
#1: 000000001cf43636 (rcu_read_lock){....}, at:
ip_local_deliver_finish+0x13d/0x390 net/ipv4/ip_input.c:231
#2: 000000005ccb0f38 (hrtimer_bases.lock){-.-.}, at:
hrtimer_interrupt+0xfc/0x780 kernel/time/hrtimer.c:1499
#3: 000000003a11d92b (&obj_hash[i].lock){-.-.}, at:
debug_object_deactivate+0xf7/0x450 lib/debugobjects.c:541
#4: 000000001cf43636 (rcu_read_lock){....}, at:
atomic_notifier_call_chain+0x0/0x190 kernel/notifier.c:329
stack backtrace:
CPU: 0 PID: 8057 Comm: syz-executor4 Not tainted 4.20.0-rc2+ #294
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
Rebooting in 86400 seconds..
---
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 syzk...@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
Dmitry Vyukov
Nov 15, 2018, 12:47:38 PM11/15/18
to syzbot, syzkaller-upst...@googlegroups.com
Maybe it's a heap corruption as we have 2 bad crashes at the same time.
Happened only once so far.
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/0000000000006c6a46057a9abca6%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Happened only once so far.
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/0000000000006c6a46057a9abca6%40google.com.
> For more options, visit https://groups.google.com/d/optout.
syzbot
Jun 7, 2019, 7:45:03 PM6/7/19
to dvy...@google.com, syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages