From: Takashi Iwai <tiwai@suse.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+194dffdb8b22fc5d207a@syzkaller.appspotmail.com>,
alsa-devel-bounces@alsa-project.org, alsa-devel@alsa-project.org,
LKML <linux-kernel@vger.kernel.org>,
Jaroslav Kysela <perex@perex.cz>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: KMSAN: uninit-value in snd_midi_event_encode_byte
Date: Mon, 03 Sep 2018 17:00:28 +0200 [thread overview]
Message-ID: <s5ho9defwxf.wl-tiwai@suse.de> (raw)
In-Reply-To: <CACT4Y+a1erpZnCVAU44wF+Sve5He4gjK4+7nGHi6RWbogfs3Ag@mail.gmail.com>
On Mon, 03 Sep 2018 16:54:23 +0200,
Dmitry Vyukov wrote:
>
> https://github.com/google/syzkaller/blob/master/docs/syzbot.md#kmsan-bugs
> is meant to be a complement to the previous generic descriptions of
> patch testing process, which is:
> https://github.com/google/syzkaller/blob/master/docs/syzbot.md#testing-patches
>
> So, you always reply to the syzbot+HASH email address so that syzbot
> understands which bug we are talking about.
> Then you do either (omitting # so that syzbot won't consider that as
> actual test requests):
>
> syz test: git://repo/address.git branch
>
> or:
>
> syz test: git://repo/address.git commit-hash
>
> And then you can either attach a patch that needs to be applied on
> top, or not attach it (if it's already in the tree, or you just want
> to get another crash report).
OK, so far, so good, it's what I knew and have done a few times.
> For KMSAN you need to issue test request against
> "https//github.com/google/kmsan.git master" (that's the only tree that
> has KMSAN tool in it) and you need to attach/inline the patch (because
> your patch is obviously not there yet).
>
> Does this make things more clear?
Sorry, the part "issue test request against https..." still isn't
clear.
Do you mean to open an issue entry on github, and attach the patch
there?
Takashi
next prev parent reply other threads:[~2018-09-03 15:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 19:29 KMSAN: uninit-value in snd_midi_event_encode_byte syzbot
2018-09-03 1:53 ` syzbot
2018-09-03 13:22 ` Takashi Iwai
2018-09-03 13:22 ` syzbot
2018-09-03 13:29 ` Takashi Iwai
2018-09-03 13:33 ` Dmitry Vyukov
2018-09-03 13:37 ` Takashi Iwai
2018-09-03 13:41 ` Dmitry Vyukov
2018-09-03 14:04 ` Takashi Iwai
2018-09-03 14:19 ` Dmitry Vyukov
2018-09-03 14:30 ` Takashi Iwai
2018-09-03 14:54 ` Dmitry Vyukov
2018-09-03 15:00 ` Takashi Iwai [this message]
2018-09-03 15:06 ` Dmitry Vyukov
2018-09-03 15:18 ` Takashi Iwai
2018-09-03 17:25 ` Dmitry Vyukov
2018-09-03 21:35 ` Takashi Iwai
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=s5ho9defwxf.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel-bounces@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=syzbot+194dffdb8b22fc5d207a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).