KASAN: use-after-free Read in rds_cong_queue_updates

36 views
Skip to first unread message

syzbot

unread,
Feb 22, 2018, 4:49:04 AM2/22/18
to da...@davemloft.net, linux-...@vger.kernel.org, linux...@vger.kernel.org, net...@vger.kernel.org, rds-...@oss.oracle.com, santosh....@oracle.com, syzkall...@googlegroups.com
Hello,

syzbot hit the following crash on upstream commit
af3e79d29555b97dd096e2f8e36a0f50213808a8 (Tue Feb 20 18:05:02 2018 +0000)
Merge tag 'leds_for-4.16-rc3' of
git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds

So far this crash happened 42 times on
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/master.
Unfortunately, I don't have any reproducer for this crash yet.
Raw console output is attached.
compiler: gcc (GCC) 7.1.1 20170620
.config is attached.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+4c20b3...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.

audit: type=1400 audit(1519244849.789:44): avc: denied { map } for
pid=6652 comm="syz-executor3" path="/dev/mixer" dev="devtmpfs" ino=172
scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023
tcontext=system_u:object_r:sound_device_t:s0 tclass=chr_file permissive=1
==================================================================
BUG: KASAN: use-after-free in __read_once_size include/linux/compiler.h:183
[inline]
BUG: KASAN: use-after-free in atomic_read arch/x86/include/asm/atomic.h:27
[inline]
BUG: KASAN: use-after-free in refcount_read include/linux/refcount.h:42
[inline]
BUG: KASAN: use-after-free in check_net include/net/net_namespace.h:228
[inline]
BUG: KASAN: use-after-free in rds_destroy_pending net/rds/rds.h:868 [inline]
BUG: KASAN: use-after-free in rds_cong_queue_updates+0x4d2/0x4f0
net/rds/cong.c:226
Read of size 4 at addr ffff8801d7800104 by task kworker/u4:7/5371

CPU: 0 PID: 5371 Comm: kworker/u4:7 Not tainted 4.16.0-rc2+ #323
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: krdsd rds_send_worker
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x194/0x257 lib/dump_stack.c:53
print_address_description+0x73/0x250 mm/kasan/report.c:256
kasan_report_error mm/kasan/report.c:354 [inline]
kasan_report+0x23b/0x360 mm/kasan/report.c:412
__asan_report_load4_noabort+0x14/0x20 mm/kasan/report.c:432
__read_once_size include/linux/compiler.h:183 [inline]
atomic_read arch/x86/include/asm/atomic.h:27 [inline]
refcount_read include/linux/refcount.h:42 [inline]
check_net include/net/net_namespace.h:228 [inline]
rds_destroy_pending net/rds/rds.h:868 [inline]
rds_cong_queue_updates+0x4d2/0x4f0 net/rds/cong.c:226
rds_recv_rcvbuf_delta.part.2+0x289/0x320 net/rds/recv.c:118
rds_recv_rcvbuf_delta net/rds/recv.c:377 [inline]
rds_recv_incoming+0xeb4/0x11d0 net/rds/recv.c:377
rds_loop_xmit+0x149/0x320 net/rds/loop.c:82
rds_send_xmit+0xbcc/0x26b0 net/rds/send.c:355
rds_send_worker+0x115/0x2a0 net/rds/threads.c:199
process_one_work+0xbbf/0x1af0 kernel/workqueue.c:2113
worker_thread+0x223/0x1990 kernel/workqueue.c:2247
kthread+0x33c/0x400 kernel/kthread.c:238
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:407

Allocated by task 4212:
save_stack+0x43/0xd0 mm/kasan/kasan.c:447
set_track mm/kasan/kasan.c:459 [inline]
kasan_kmalloc+0xad/0xe0 mm/kasan/kasan.c:552
kasan_slab_alloc+0x12/0x20 mm/kasan/kasan.c:489
kmem_cache_alloc+0x12e/0x760 mm/slab.c:3541
kmem_cache_zalloc include/linux/slab.h:691 [inline]
net_alloc net/core/net_namespace.c:369 [inline]
copy_net_ns+0x152/0x580 net/core/net_namespace.c:409
create_new_namespaces+0x425/0x880 kernel/nsproxy.c:107
unshare_nsproxy_namespaces+0xae/0x1e0 kernel/nsproxy.c:206
SYSC_unshare kernel/fork.c:2418 [inline]
SyS_unshare+0x653/0xfa0 kernel/fork.c:2368
do_syscall_64+0x280/0x940 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x42/0xb7

Freed by task 5371:
save_stack+0x43/0xd0 mm/kasan/kasan.c:447
set_track mm/kasan/kasan.c:459 [inline]
__kasan_slab_free+0x11a/0x170 mm/kasan/kasan.c:520
kasan_slab_free+0xe/0x10 mm/kasan/kasan.c:527
__cache_free mm/slab.c:3485 [inline]
kmem_cache_free+0x83/0x2a0 mm/slab.c:3743
net_free+0xca/0x110 net/core/net_namespace.c:385
net_drop_ns.part.11+0x26/0x30 net/core/net_namespace.c:392
net_drop_ns net/core/net_namespace.c:391 [inline]
cleanup_net+0x977/0xcb0 net/core/net_namespace.c:535
process_one_work+0xbbf/0x1af0 kernel/workqueue.c:2113
worker_thread+0x223/0x1990 kernel/workqueue.c:2247
kthread+0x33c/0x400 kernel/kthread.c:238
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:407

The buggy address belongs to the object at ffff8801d7800100
which belongs to the cache net_namespace of size 6720
The buggy address is located 4 bytes inside of
6720-byte region [ffff8801d7800100, ffff8801d7801b40)
The buggy address belongs to the page:
page:ffffea00075e0000 count:1 mapcount:0 mapping:ffff8801d7800100 index:0x0
compound_mapcount: 0
flags: 0x2fffc0000008100(slab|head)
raw: 02fffc0000008100 ffff8801d7800100 0000000000000000 0000000100000001
raw: ffffea0006cf4020 ffffea00071dbda0 ffff8801d9feae00 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff8801d7800000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff8801d7800080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
> ffff8801d7800100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff8801d7800180: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff8801d7800200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.

syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
raw.log.txt
config.txt

syzbot

unread,
Jun 12, 2018, 10:51:03 PM6/12/18
to da...@davemloft.net, linux-...@vger.kernel.org, linux...@vger.kernel.org, net...@vger.kernel.org, rds-...@oss.oracle.com, santosh....@oracle.com, syzkall...@googlegroups.com
syzbot has found a reproducer for the following crash on:

HEAD commit: f0dc7f9c6dd9 Merge git://git.kernel.org/pub/scm/linux/kern..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1461f03f800000
kernel config: https://syzkaller.appspot.com/x/.config?x=fa9c20c48788d1c1
dashboard link: https://syzkaller.appspot.com/bug?extid=4c20b3866171ce8441d2
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=16cbfeaf800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=165227f7800000

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+4c20b3...@syzkaller.appspotmail.com

IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
8021q: adding VLAN 0 to HW filter on device team0
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
==================================================================
BUG: KASAN: use-after-free in atomic_read
include/asm-generic/atomic-instrumented.h:21 [inline]
BUG: KASAN: use-after-free in refcount_read include/linux/refcount.h:42
[inline]
BUG: KASAN: use-after-free in check_net include/net/net_namespace.h:236
[inline]
BUG: KASAN: use-after-free in rds_destroy_pending net/rds/rds.h:897 [inline]
BUG: KASAN: use-after-free in rds_cong_queue_updates+0x255/0x590
net/rds/cong.c:226
Read of size 4 at addr ffff8801ab180044 by task syz-executor199/4800

CPU: 1 PID: 4800 Comm: syz-executor199 Not tainted 4.17.0+ #84
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1b9/0x294 lib/dump_stack.c:113
print_address_description+0x6c/0x20b mm/kasan/report.c:256
kasan_report_error mm/kasan/report.c:354 [inline]
kasan_report.cold.7+0x242/0x2fe 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_read include/linux/refcount.h:42 [inline]
check_net include/net/net_namespace.h:236 [inline]
rds_destroy_pending net/rds/rds.h:897 [inline]
rds_cong_queue_updates+0x255/0x590 net/rds/cong.c:226
rds_recv_rcvbuf_delta.part.3+0x211/0x350 net/rds/recv.c:126
rds_recv_rcvbuf_delta net/rds/recv.c:735 [inline]
rds_clear_recv_queue+0x2f0/0x4c0 net/rds/recv.c:735
rds_release+0x15c/0x550 net/rds/af_rds.c:72
__sock_release+0xd7/0x260 net/socket.c:603
sock_close+0x19/0x20 net/socket.c:1186
__fput+0x353/0x890 fs/file_table.c:209
____fput+0x15/0x20 fs/file_table.c:243
task_work_run+0x1e4/0x290 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x1aee/0x2730 kernel/exit.c:865
do_group_exit+0x16f/0x430 kernel/exit.c:968
get_signal+0x886/0x1960 kernel/signal.c:2468
do_signal+0x9c/0x21c0 arch/x86/kernel/signal.c:816
exit_to_usermode_loop+0x2cf/0x360 arch/x86/entry/common.c:162
prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
syscall_return_slowpath arch/x86/entry/common.c:268 [inline]
do_syscall_64+0x6ac/0x800 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x44f439
Code: e8 ac be 02 00 48 83 c4 18 c3 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 0f 83 5b ff fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fc65567dcf8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00000000006edadc RCX: 000000000044f439
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000006edadc
RBP: 00000000006edad8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff3df31b1f R14: 00007fc65567e9c0 R15: 0000000000000061

Allocated by task 4800:
save_stack+0x43/0xd0 mm/kasan/kasan.c:448
set_track mm/kasan/kasan.c:460 [inline]
kasan_kmalloc+0xc4/0xe0 mm/kasan/kasan.c:553
kasan_slab_alloc+0x12/0x20 mm/kasan/kasan.c:490
kmem_cache_alloc+0x12e/0x760 mm/slab.c:3554
kmem_cache_zalloc include/linux/slab.h:696 [inline]
net_alloc net/core/net_namespace.c:383 [inline]
copy_net_ns+0x159/0x4c0 net/core/net_namespace.c:423
create_new_namespaces+0x69d/0x8f0 kernel/nsproxy.c:107
unshare_nsproxy_namespaces+0xc3/0x1f0 kernel/nsproxy.c:206
ksys_unshare+0x708/0xf90 kernel/fork.c:2411
__do_sys_unshare kernel/fork.c:2479 [inline]
__se_sys_unshare kernel/fork.c:2477 [inline]
__x64_sys_unshare+0x31/0x40 kernel/fork.c:2477
do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe

Freed by task 746:
save_stack+0x43/0xd0 mm/kasan/kasan.c:448
set_track mm/kasan/kasan.c:460 [inline]
__kasan_slab_free+0x11a/0x170 mm/kasan/kasan.c:521
kasan_slab_free+0xe/0x10 mm/kasan/kasan.c:528
__cache_free mm/slab.c:3498 [inline]
kmem_cache_free+0x86/0x2d0 mm/slab.c:3756
net_free net/core/net_namespace.c:399 [inline]
net_drop_ns.part.14+0x11a/0x130 net/core/net_namespace.c:406
net_drop_ns net/core/net_namespace.c:405 [inline]
cleanup_net+0x6a1/0xb20 net/core/net_namespace.c:541
process_one_work+0xc64/0x1b70 kernel/workqueue.c:2153
worker_thread+0x181/0x13a0 kernel/workqueue.c:2296
kthread+0x345/0x410 kernel/kthread.c:240
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:412

The buggy address belongs to the object at ffff8801ab180040
which belongs to the cache net_namespace(17:syz0) of size 8896
The buggy address is located 4 bytes inside of
8896-byte region [ffff8801ab180040, ffff8801ab182300)
The buggy address belongs to the page:
page:ffffea0006ac6000 count:1 mapcount:0 mapping:ffff8801aeaa0080 index:0x0
compound_mapcount: 0
flags: 0x2fffc0000008100(slab|head)
raw: 02fffc0000008100 ffff8801d3827048 ffff8801d3827048 ffff8801aeaa0080
raw: 0000000000000000 ffff8801ab180040 0000000100000001 ffff8801ab7cae40
page dumped because: kasan: bad access detected
page->mem_cgroup:ffff8801ab7cae40

Memory state around the buggy address:
ffff8801ab17ff00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff8801ab17ff80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ffff8801ab180000: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb
^
ffff8801ab180080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff8801ab180100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================

Dmitry Vyukov

unread,
Jun 13, 2018, 3:52:06 AM6/13/18
to syzbot, Sowmini Varadhan, David Miller, LKML, linux...@vger.kernel.org, netdev, rds-...@oss.oracle.com, Santosh Shilimkar, syzkaller-bugs
On Wed, Jun 13, 2018 at 4:51 AM, syzbot
<syzbot+4c20b3...@syzkaller.appspotmail.com> wrote:
> syzbot has found a reproducer for the following crash on:

Woohoo! Please take a look, this is a top crasher.
> ^
> ffff8801ab180080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
> ffff8801ab180100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
> ==================================================================
>
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-bugs/000000000000a643e4056e7d0db4%40google.com.
>
> For more options, visit https://groups.google.com/d/optout.

santosh....@oracle.com

unread,
Jun 13, 2018, 3:54:22 AM6/13/18
to Dmitry Vyukov, syzbot, Sowmini Varadhan, David Miller, LKML, linux...@vger.kernel.org, netdev, rds-...@oss.oracle.com, syzkaller-bugs


On 6/13/18 12:51 AM, Dmitry Vyukov wrote:
> On Wed, Jun 13, 2018 at 4:51 AM, syzbot
> <syzbot+4c20b3...@syzkaller.appspotmail.com> wrote:
>> syzbot has found a reproducer for the following crash on:
>
> Woohoo! Please take a look, this is a top crasher.
>
Will have a look Dmitry !!

Sowmini Varadhan

unread,
Jun 26, 2018, 11:26:57 AM6/26/18
to syzkaller-bugs
0001-rds-clean-up-loopback-rds_connections-on-netns-delet.patch

syzbot

unread,
Jun 26, 2018, 11:26:59 AM6/26/18
to Sowmini Varadhan, sowmini....@oracle.com, syzkall...@googlegroups.com
Can't find the corresponding bug.


> --
> You received this message because you are subscribed to the Google
> Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-bugs/20180626152647.GK20575%40oracle.com.

Sowmini Varadhan

unread,
Jun 26, 2018, 11:29:52 AM6/26/18
to dvy...@google.com, syzkall...@googlegroups.com

What does "cant find the corresponding bug" mean?
What did I need to provide?

----- Forwarded message from syzbot <syz...@syzkaller.appspotmail.com> -----

> Date: Tue, 26 Jun 2018 08:26:58 -0700
> From: syzbot <syz...@syzkaller.appspotmail.com>
> To: Sowmini Varadhan <sowmini....@oracle.com>
> Cc: sowmini....@oracle.com, syzkall...@googlegroups.com
> Subject: Re: Re: KASAN: use-after-free Read in rds_cong_queue_updates
>
>
> >>HEAD commit: f0dc7f9c6dd9 Merge
> >>git://git.kernel.org/pub/scm/linux/kern..
> >>git tree: net-next
> >>console output: https://urldefense.proofpoint.com/v2/url?u=https-3A__syzkaller.appspot.com_x_log.txt-3Fx-3D1461f03f800000&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=GFriBKgrVvoJNWWUXr74TXXfMHW6ZTEDcHbO2Avqg5U&m=mb1qjwm5v5ZmDZd31x-Um5euArZO9B6xR6MGifJ0OuQ&s=DRG3OW_yIuh2W0KpWZ6fLRVOTvnpwZF-ruN__3dUxPw&e=
> >>kernel config: https://urldefense.proofpoint.com/v2/url?u=https-3A__syzkaller.appspot.com_x_.config-3Fx-3Dfa9c20c48788d1c1&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=GFriBKgrVvoJNWWUXr74TXXfMHW6ZTEDcHbO2Avqg5U&m=mb1qjwm5v5ZmDZd31x-Um5euArZO9B6xR6MGifJ0OuQ&s=PLLX_svLpt0NzjGRVIqDH7EKuzTXhQFiYnCPG4YXWbU&e=
> >>dashboard link: https://urldefense.proofpoint.com/v2/url?u=https-3A__syzkaller.appspot.com_bug-3Fextid-3D4c20b3866171ce8441d2&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=GFriBKgrVvoJNWWUXr74TXXfMHW6ZTEDcHbO2Avqg5U&m=mb1qjwm5v5ZmDZd31x-Um5euArZO9B6xR6MGifJ0OuQ&s=BkU9izu5jKQhhzwsMV05ADYmrfsZBrihZETBH9uK1_o&e=
> >>compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> >>syzkaller repro:https://urldefense.proofpoint.com/v2/url?u=https-3A__syzkaller.appspot.com_x_repro.syz-3Fx-3D16cbfeaf800000&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=GFriBKgrVvoJNWWUXr74TXXfMHW6ZTEDcHbO2Avqg5U&m=mb1qjwm5v5ZmDZd31x-Um5euArZO9B6xR6MGifJ0OuQ&s=Q4N_ajKMyYG3F1X8d3ArvEZvBlBQGVWzidctkrQPez4&e=
> >>C reproducer: https://urldefense.proofpoint.com/v2/url?u=https-3A__syzkaller.appspot.com_x_repro.c-3Fx-3D165227f7800000&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=GFriBKgrVvoJNWWUXr74TXXfMHW6ZTEDcHbO2Avqg5U&m=mb1qjwm5v5ZmDZd31x-Um5euArZO9B6xR6MGifJ0OuQ&s=OJ4Fmxv2HG1XCOOqgvQDdL6ntegDF0G3NM9cY5-o5Ao&e=
>
>
> >#syz test:
> >git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
>
> Can't find the corresponding bug.
>
>
> >--
> >You received this message because you are subscribed to the Google Groups
> >"syzkaller-bugs" group.
> >To unsubscribe from this group and stop receiving emails from it, send an
> >email to syzkaller-bug...@googlegroups.com.
> >To view this discussion on the web visit https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_msgid_syzkaller-2Dbugs_20180626152647.GK20575-2540oracle.com&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=GFriBKgrVvoJNWWUXr74TXXfMHW6ZTEDcHbO2Avqg5U&m=mb1qjwm5v5ZmDZd31x-Um5euArZO9B6xR6MGifJ0OuQ&s=9B-WkrDVzEo9bfUN4f3EKrPFDHDBtSU5xK1XJT8S-gc&e=.
> >For more options, visit https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=GFriBKgrVvoJNWWUXr74TXXfMHW6ZTEDcHbO2Avqg5U&m=mb1qjwm5v5ZmDZd31x-Um5euArZO9B6xR6MGifJ0OuQ&s=-ChUOES-8TSC1s9O9kQ8ZTNvwUcNKLToRpl5uGnP4FU&e=.

----- End forwarded message -----

Dmitry Vyukov

unread,
Jun 26, 2018, 11:35:39 AM6/26/18
to Sowmini Varadhan, syzkaller-bugs
On Tue, Jun 26, 2018 at 5:29 PM, Sowmini Varadhan
<sowmini....@oracle.com> wrote:
>
> What does "cant find the corresponding bug" mean?
> What did I need to provide?

You need to reply to syzbot email (actually, just send an email with
the corresponding syzbot email address in To). The emails look like
syzbo...@syzkaller.appspotmail.com This allows it to figure out
what exactly bug you are referring to.
You can also find this email address on the dashboard:
https://syzkaller.appspot.com/bug?id=f4ef381349e100280193c25f24e01d9d364132d9

syzbot

unread,
Jun 26, 2018, 12:25:03 PM6/26/18
to sowmini....@oracle.com, syzkall...@googlegroups.com
Hello,

syzbot has tested the proposed patch and the reproducer did not trigger
crash:

Reported-and-tested-by:
syzbot+4c20b3...@syzkaller.appspotmail.com

Tested on:

commit: 27a2628b3c24 selftests: forwarding: mirror_gre_vlan_bridge..
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=a63be0c83e84d370
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
patch: https://syzkaller.appspot.com/x/patch.diff?x=13482590400000

Note: testing is done by a robot and is best-effort only.
Reply all
Reply to author
Forward
0 new messages