archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <>
To: Corentin Labbe <>,,,,,
Subject: Re: BUG: cryptsetup benchmark stuck
Date: Mon, 16 Mar 2020 09:28:40 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20200315145214.GA9576@Red>


Corentin Labbe <> 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")



  reply	other threads:[~2020-03-16  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 14:52 Corentin Labbe
2020-03-16  8:28 ` Thomas Gleixner [this message]
2020-03-16 13:53   ` Corentin Labbe

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: BUG: cryptsetup benchmark stuck' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).