linux-kernel - Re: crypto: ablk_decrypt causes BUG in scatterwalk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACT4Y+Y6NFH1Q9=HCW=jYmCKRewnjUpWD6Xv-+F5B5=APWFT6A@mail.gmail.com>
Date:	Tue, 12 Jan 2016 18:09:17 +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

I can _not_ reproduce it on clean upstream tree, nor on
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git.
I probably messed up something with the unmerged fixes during my rebase.
Sorry.



On Tue, Jan 12, 2016 at 5:27 PM, Dmitry Vyukov <dvyukov@...gle.com> wrote:
> 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.