[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eeb6d178dff61dfebf5a3ce9675486a3271b748c.camel@intel.com>
Date: Mon, 29 Jan 2024 22:23:58 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "peterz@...radead.org" <peterz@...radead.org>, "stli@...ux.ibm.com"
<stli@...ux.ibm.com>
CC: "xry111@...111.site" <xry111@...111.site>, "hca@...ux.ibm.com"
<hca@...ux.ibm.com>, "andrealmeid@...lia.com" <andrealmeid@...lia.com>,
"fweimer@...hat.com" <fweimer@...hat.com>, "linux-mm@...ck.org"
<linux-mm@...ck.org>, "libc-alpha@...rceware.org"
<libc-alpha@...rceware.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "tglx@...utronix.de" <tglx@...utronix.de>,
"svens@...ux.ibm.com" <svens@...ux.ibm.com>, "linux-api@...r.kernel.org"
<linux-api@...r.kernel.org>, "linux-arch@...r.kernel.org"
<linux-arch@...r.kernel.org>
Subject: Re: Several tst-robust* tests time out with recent Linux kernel
On Fri, 2024-01-19 at 14:56 +0100, Stefan Liebler wrote:
> I've reduced the test (see attachement) and now have only one process
> with three threads.
This tests fails on my setup as well:
main: start 3 threads.
#0: started: fct=1
#1: started: fct=1
#2: started: fct=1
#2: mutex_timedlock failed with 22 (round=28772)
But, after this patch:
https://lore.kernel.org/all/20240116130810.ji1YCxpg@linutronix.de/
...the attached test hangs.
However, the glibc test that was failing for me "nptl/tst-robustpi8"
passes with the linked patch applied. So I think that patch fixes the
issue I hit.
What is passing supposed to look like on the attached test?
Powered by blists - more mailing lists