From: Greg KH <gregkh@linuxfoundation.org>
To: syzbot <syzbot+a7e220df5a81d1ab400e@syzkaller.appspotmail.com>
Cc: andreyknvl@google.com, balbi@kernel.org,
dan.carpenter@oracle.com, glider@google.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KMSAN: kernel-infoleak in raw_ioctl
Date: Mon, 10 Aug 2020 09:47:06 +0200 [thread overview]
Message-ID: <20200810074706.GD1529187@kroah.com> (raw)
In-Reply-To: <000000000000ce85c405ac744ff6@google.com>
On Sun, Aug 09, 2020 at 09:27:18AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: ce8056d1 wip: changed copy_from_user where instrumented
> git tree: https://github.com/google/kmsan.git master
> console output: https://syzkaller.appspot.com/x/log.txt?x=141eb8b2900000
> kernel config: https://syzkaller.appspot.com/x/.config?x=3afe005fb99591f
> dashboard link: https://syzkaller.appspot.com/bug?extid=a7e220df5a81d1ab400e
> compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
> userspace arch: i386
>
> Unfortunately, I don't have any reproducer for this issue yet.
The irony of a kernel module written for syzbot testing, causing syzbot
reports....
next prev parent reply other threads:[~2020-08-10 7:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 16:27 KMSAN: kernel-infoleak in raw_ioctl syzbot
2020-08-10 7:47 ` Greg KH [this message]
2020-08-10 9:00 ` Dmitry Vyukov
2020-08-10 9:08 ` Greg KH
2020-08-10 9:15 ` Greg KH
2020-08-10 9:57 ` Greg KH
2020-08-10 10:21 ` Dmitry Vyukov
2020-08-10 11:06 ` Greg KH
2020-08-10 14:07 ` Andrey Konovalov
2020-08-10 14:17 ` Dmitry Vyukov
2020-08-19 6:33 ` syzbot
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=20200810074706.GD1529187@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreyknvl@google.com \
--cc=balbi@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+a7e220df5a81d1ab400e@syzkaller.appspotmail.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.