Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Thomas Gleixner <tglx@linutronix.de>
To:     Corentin Labbe <clabbe.montjoie@gmail.com>, peterz@infradead.org,
        herbert@gondor.apana.org.au, viro@zeniv.linux.org.uk,
        mingo@redhat.com, dvhart@infradead.org
Cc:     linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: cryptsetup benchmark stuck
In-Reply-To: <20200315145214.GA9576@Red>
References: <20200315145214.GA9576@Red>
Date:   Mon, 16 Mar 2020 09:28:40 +0100
Message-ID: <877dzkem9z.fsf@nanos.tec.linutronix.de>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

Corentin,

Corentin Labbe <clabbe.montjoie@gmail.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")

Thanks,

        tglx