From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: peterz@infradead.org, herbert@gondor.apana.org.au,
viro@zeniv.linux.org.uk, mingo@redhat.com, dvhart@infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: cryptsetup benchmark stuck
Date: Mon, 16 Mar 2020 14:53:18 +0100 [thread overview]
Message-ID: <20200316135318.GA29789@Red> (raw)
In-Reply-To: <877dzkem9z.fsf@nanos.tec.linutronix.de>
On Mon, Mar 16, 2020 at 09:28:40AM +0100, Thomas Gleixner wrote:
> 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")
>
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
prev parent reply other threads:[~2020-03-16 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 14:52 BUG: cryptsetup benchmark stuck Corentin Labbe
2020-03-16 8:28 ` Thomas Gleixner
2020-03-16 13:53 ` Corentin Labbe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200316135318.GA29789@Red \
--to=clabbe.montjoie@gmail.com \
--cc=dvhart@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.