From: syzbot <syzbot+ab504332a376ca03331e@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, ebiederm@xmission.com,
ldv@altlinux.org, linux-kernel@vger.kernel.org,
linux@dominikbrodowski.net, oleg@redhat.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: KMSAN: uninit-value in copy_siginfo_to_user
Date: Tue, 17 Jul 2018 06:23:02 -0700 [thread overview]
Message-ID: <0000000000007ae01e057131d872@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 8fc8ecd1c58a kmsan: unpoison regs in arch_uprobe_exception..
git tree: https://github.com/google/kmsan.git/master
console output: https://syzkaller.appspot.com/x/log.txt?x=1758708f800000
kernel config: https://syzkaller.appspot.com/x/.config?x=9fa436d3ae606638
dashboard link: https://syzkaller.appspot.com/bug?extid=ab504332a376ca03331e
compiler: clang version 7.0.0 (trunk 332596)
syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=170eeed7800000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+ab504332a376ca03331e@syzkaller.appspotmail.com
IPv6: ADDRCONF(NETDEV_UP): veth1: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
8021q: adding VLAN 0 to HW filter on device team0
==================================================================
BUG: KMSAN: uninit-value in copy_siginfo_to_user+0x383/0x1270
kernel/signal.c:2870
CPU: 1 PID: 4746 Comm: syz-executor0 Not tainted 4.17.0-rc5+ #103
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+0x185/0x1d0 lib/dump_stack.c:113
kmsan_report+0x149/0x260 mm/kmsan/kmsan.c:1084
__msan_warning_32+0x6e/0xc0 mm/kmsan/kmsan_instr.c:686
copy_siginfo_to_user+0x383/0x1270 kernel/signal.c:2870
ptrace_peek_siginfo kernel/ptrace.c:741 [inline]
ptrace_request+0x1d6a/0x20e0 kernel/ptrace.c:912
arch_ptrace+0x1f6/0x1230 arch/x86/kernel/ptrace.c:877
__do_sys_ptrace kernel/ptrace.c:1145 [inline]
__se_sys_ptrace+0x309/0x850 kernel/ptrace.c:1110
__x64_sys_ptrace+0x11e/0x170 kernel/ptrace.c:1110
do_syscall_64+0x152/0x230 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x455a09
RSP: 002b:00007ffc971089c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000065
RAX: ffffffffffffffda RBX: 0000000000acf914 RCX: 0000000000455a09
RDX: 0000000000730004 RSI: 0000000000000001 RDI: 0000000000004209
RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000558 R14: 00000000006fd0e0 R15: 000000000000b0fe
Local variable description: ----kiov@ptrace_request
Variable was created at:
ptrace_request+0x194/0x20e0 kernel/ptrace.c:885
arch_ptrace+0x1f6/0x1230 arch/x86/kernel/ptrace.c:877
==================================================================
---
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#bug-status-tracking 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:[~2018-07-17 13:23 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=0000000000007ae01e057131d872@google.com \
--to=syzbot+ab504332a376ca03331e@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=oleg@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome