linux-kernel - Re: BUG: cryptsetup benchmark stuck

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] [day] [month] [year] [list]

Message-ID: <20200316135318.GA29789@Red>
Date:   Mon, 16 Mar 2020 14:53:18 +0100
From:   Corentin Labbe <clabbe.montjoie@...il.com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     peterz@...radead.org, herbert@...dor.apana.org.au,
        viro@...iv.linux.org.uk, mingo@...hat.com, dvhart@...radead.org,
        linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: BUG: cryptsetup benchmark stuck

On Mon, Mar 16, 2020 at 09:28:40AM +0100, Thomas Gleixner wrote:
> Corentin,
> 
> Corentin Labbe <clabbe.montjoie@...il.com> writes:
> > On next-20200313, running cryptsetup benchmark is stuck.
> > I have bisected this problem twice and the result is the same:
> >
> > git bisect bad 8019ad13ef7f64be44d4f892af9c840179009254
> > # first bad commit: [8019ad13ef7f64be44d4f892af9c840179009254] futex: Fix inode life-time issue
> >
> > Since the two bisect lead to the same commit, I think it should be
> > right one even if I dont find anything related to my problem.
> 
> I'm as puzzled as you.
> 
> > But reverting this patch is impossible, so I cannot test to try
> > without it.
> 
> You need to revert two:
> 
> 8d67743653dc ("futex: Unbreak futex hashing")
> 8019ad13ef7f ("futex: Fix inode life-time issue")
> 

On next-20200313, there are no "futex: Unbreak futex hashing".
And it seems to fix my issue, I have updated to next-20200316 (which have it) and the issue is not present anymore.

Thanks
Regards