[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+aFyPyZHV5TnW_Z_MMgEunS0F1V-dvBqzSbSGeWU_TNYw@mail.gmail.com>
Date: Tue, 12 Jan 2016 17:27:53 +0100
From: Dmitry Vyukov <dvyukov@...gle.com>
To: syzkaller <syzkaller@...glegroups.com>
Cc: "David S. Miller" <davem@...emloft.net>,
linux-crypto@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Kostya Serebryany <kcc@...gle.com>,
Alexander Potapenko <glider@...gle.com>,
Sasha Levin <sasha.levin@...cle.com>,
Eric Dumazet <edumazet@...gle.com>
Subject: Re: crypto: ablk_decrypt causes BUG in scatterwalk
On Tue, Jan 12, 2016 at 2:23 PM, Dmitry Vyukov <dvyukov@...gle.com> wrote:
> On Tue, Jan 12, 2016 at 2:16 PM, Herbert Xu <herbert@...dor.apana.org.au> wrote:
>> On Tue, Jan 12, 2016 at 10:27:44AM +0100, Dmitry Vyukov wrote:
>>> Hello,
>>>
>>> The following program cause BUG in scatterwalk:
>>
>> Weird, I can't reproduce the crash. Can you perhaps convert this to
>> a non-racy reproduction, possibly by using strace to find the order
>> of execution that leads to the crash?
>
>
> Concurrent execution seems to be important to reproduce the crash. I
> wasn't able to reproduce it in single-threaded mode.
> Try to run it in a tight parallel loop for some time.
I've extracted another reproducer:
https://gist.githubusercontent.com/dvyukov/94aed45494edf1dff0a8/raw/a31f439fdcdd8a8905235a9bce6e5863ca8ccf68/gistfile1.txt
I don't know whether there is a simpler way to run a reproducer in a
tight parallel loop, but I use:
$ go get golang.org/x/tools/cmd/stress
$ GOPATH/bin/stress -p 16 ./a.out
It triggers the BUG within seconds for me.
Powered by blists - more mailing lists