From: syzbot <syzbot+301cccce1b286fa6449e@syzkaller.appspotmail.com>
To: ap420073@gmail.com, davem@davemloft.net,
dong.menglong@zte.com.cn, edumazet@google.com, glider@google.com,
linux-kernel@vger.kernel.org, maheshb@google.com,
netdev@vger.kernel.org, richardcochran@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: KMSAN: uninit-value in macvlan_start_xmit
Date: Mon, 29 Jun 2020 09:11:16 -0700 [thread overview]
Message-ID: <000000000000fa90bb05a93b4e52@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: f0d5ec90 kmsan: apply __no_sanitize_memory to dotraplinkag..
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1565759b100000
kernel config: https://syzkaller.appspot.com/x/.config?x=86e4f8af239686c6
dashboard link: https://syzkaller.appspot.com/bug?extid=301cccce1b286fa6449e
compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=132ae8f5100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=156200f3100000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+301cccce1b286fa6449e@syzkaller.appspotmail.com
=====================================================
BUG: KMSAN: uninit-value in macvlan_queue_xmit drivers/net/macvlan.c:521 [inline]
BUG: KMSAN: uninit-value in macvlan_start_xmit+0x3ea/0xb50 drivers/net/macvlan.c:562
CPU: 0 PID: 9 Comm: ksoftirqd/0 Not tainted 5.7.0-rc4-syzkaller #0
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+0x1c9/0x220 lib/dump_stack.c:118
kmsan_report+0xf7/0x1e0 mm/kmsan/kmsan_report.c:121
__msan_warning+0x58/0xa0 mm/kmsan/kmsan_instr.c:215
macvlan_queue_xmit drivers/net/macvlan.c:521 [inline]
macvlan_start_xmit+0x3ea/0xb50 drivers/net/macvlan.c:562
__netdev_start_xmit include/linux/netdevice.h:4533 [inline]
netdev_start_xmit include/linux/netdevice.h:4547 [inline]
xmit_one net/core/dev.c:3477 [inline]
dev_hard_start_xmit+0x531/0xab0 net/core/dev.c:3493
__dev_queue_xmit+0x2f8d/0x3b20 net/core/dev.c:4052
dev_queue_xmit+0x4b/0x60 net/core/dev.c:4085
hsr_xmit net/hsr/hsr_forward.c:228 [inline]
hsr_forward_do net/hsr/hsr_forward.c:285 [inline]
hsr_forward_skb+0x2614/0x30d0 net/hsr/hsr_forward.c:361
hsr_handle_frame+0x3be/0x500 net/hsr/hsr_slave.c:44
__netif_receive_skb_core+0x21ce/0x5870 net/core/dev.c:5089
__netif_receive_skb_one_core net/core/dev.c:5186 [inline]
__netif_receive_skb net/core/dev.c:5302 [inline]
process_backlog+0x936/0x1410 net/core/dev.c:6134
napi_poll net/core/dev.c:6572 [inline]
net_rx_action+0x786/0x1aa0 net/core/dev.c:6640
__do_softirq+0x311/0x83d kernel/softirq.c:293
run_ksoftirqd+0x25/0x40 kernel/softirq.c:608
smpboot_thread_fn+0x493/0x980 kernel/smpboot.c:165
kthread+0x4b5/0x4f0 kernel/kthread.c:269
ret_from_fork+0x35/0x40 arch/x86/entry/entry_64.S:353
Uninit was stored to memory at:
kmsan_save_stack_with_flags mm/kmsan/kmsan.c:144 [inline]
kmsan_internal_chain_origin+0xad/0x130 mm/kmsan/kmsan.c:310
kmsan_memcpy_memmove_metadata+0x272/0x2e0 mm/kmsan/kmsan.c:247
kmsan_memcpy_metadata+0xb/0x10 mm/kmsan/kmsan.c:267
__msan_memcpy+0x43/0x50 mm/kmsan/kmsan_instr.c:116
pskb_expand_head+0x38b/0x1b00 net/core/skbuff.c:1636
__skb_pad+0x47f/0x900 net/core/skbuff.c:1804
__skb_put_padto include/linux/skbuff.h:3244 [inline]
skb_put_padto include/linux/skbuff.h:3263 [inline]
send_hsr_supervision_frame+0x122d/0x1500 net/hsr/hsr_device.c:301
hsr_announce+0x1e2/0x370 net/hsr/hsr_device.c:332
call_timer_fn+0x218/0x510 kernel/time/timer.c:1405
expire_timers kernel/time/timer.c:1450 [inline]
__run_timers+0xcff/0x1210 kernel/time/timer.c:1774
run_timer_softirq+0x2d/0x50 kernel/time/timer.c:1787
__do_softirq+0x311/0x83d kernel/softirq.c:293
Uninit was created at:
kmsan_save_stack_with_flags+0x3c/0x90 mm/kmsan/kmsan.c:144
kmsan_internal_alloc_meta_for_pages mm/kmsan/kmsan_shadow.c:269 [inline]
kmsan_alloc_page+0xb9/0x180 mm/kmsan/kmsan_shadow.c:293
__alloc_pages_nodemask+0x56a2/0x5dc0 mm/page_alloc.c:4848
__alloc_pages include/linux/gfp.h:504 [inline]
__alloc_pages_node include/linux/gfp.h:517 [inline]
alloc_pages_node include/linux/gfp.h:531 [inline]
__page_frag_cache_refill mm/page_alloc.c:4923 [inline]
page_frag_alloc+0x3ae/0x910 mm/page_alloc.c:4953
__napi_alloc_skb+0x193/0xa60 net/core/skbuff.c:519
napi_alloc_skb include/linux/skbuff.h:2876 [inline]
page_to_skb+0x1a2/0x1390 drivers/net/virtio_net.c:384
receive_mergeable drivers/net/virtio_net.c:935 [inline]
receive_buf+0xec6/0x8d20 drivers/net/virtio_net.c:1045
virtnet_receive drivers/net/virtio_net.c:1335 [inline]
virtnet_poll+0x64b/0x19f0 drivers/net/virtio_net.c:1440
napi_poll net/core/dev.c:6572 [inline]
net_rx_action+0x786/0x1aa0 net/core/dev.c:6640
__do_softirq+0x311/0x83d kernel/softirq.c:293
=====================================================
---
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.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2020-06-29 21:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000fa90bb05a93b4e52@google.com \
--to=syzbot+301cccce1b286fa6449e@syzkaller.appspotmail.com \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=dong.menglong@zte.com.cn \
--cc=edumazet@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.