[lkml]   [2018]   [Sep]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: KMSAN: uninit-value in snd_midi_event_encode_byte
On Mon, Sep 3, 2018 at 5:00 PM, Takashi Iwai <> wrote:
> On Mon, 03 Sep 2018 16:54:23 +0200,
> Dmitry Vyukov wrote:
>> is meant to be a complement to the previous generic descriptions of
>> patch testing process, which is:
>> 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// 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?

By "issue test request" I mean sending email with "syz test" command.
So overall you send "syz test https//
master" and attach the patch.
The workflow is all the same, and no github involved. It's just that
you can't ask to test it against
git:// because
it does not have KMSAN tool and so no KMSAN bugs will be detected

Since I did all of this, it's hard for me to write clear docs for others. Sorry.
If you can suggest some improved wording, it would be great.

 \ /
  Last update: 2018-09-03 17:06    [W:0.064 / U:0.328 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site