[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+b5JS5BboDz4Z92KoHpp6HEp-SByzWDAXARrLJtyR0Aug@mail.gmail.com>
Date: Fri, 6 Jul 2018 09:44:23 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Stephan Mueller <smueller@...onox.de>
Cc: syzbot <syzbot+9c251bdd09f83b92ba95@...kaller.appspotmail.com>,
David Miller <davem@...emloft.net>,
Herbert Xu <herbert@...dor.apana.org.au>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: KMSAN: uninit-value in af_alg_free_areq_sgls
On Fri, Jul 6, 2018 at 9:41 AM, Stephan Mueller <smueller@...onox.de> wrote:
> Am Freitag, 6. Juli 2018, 09:38:41 CEST schrieb Dmitry Vyukov:
>
> Hi Dmitry,
>
>> On Thu, Jul 5, 2018 at 8:45 PM, Stephan Müller <smueller@...onox.de> wrote:
>> > Am Donnerstag, 5. Juli 2018, 19:02:01 CEST schrieb syzbot:
>> >
>> > Hi Dimitry,
>> >
>> > does the syzkaller somehow uses the "---" separator as part of the URL?
>>
>> It used it as branch. Please see:
>>
>> https://github.com/google/syzkaller/blob/master/docs/syzbot.md#testing-patch
>> es
>>
>> for formats. In all formats a git tree is not enough. And it is not
>> enough to identify code state in any other context too, it's always
>> git repo + branch or commit hash.
>
> And which branch should I use for the kmsan.git repo?
master, as specified in the original syzbot report. I will add this to
the doc too.
Powered by blists - more mailing lists