From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "peterz@infradead.org" <peterz@infradead.org>,
"stli@linux.ibm.com" <stli@linux.ibm.com>
Cc: "xry111@xry111.site" <xry111@xry111.site>,
"hca@linux.ibm.com" <hca@linux.ibm.com>,
"andrealmeid@igalia.com" <andrealmeid@igalia.com>,
"fweimer@redhat.com" <fweimer@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"svens@linux.ibm.com" <svens@linux.ibm.com>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: Several tst-robust* tests time out with recent Linux kernel
Date: Mon, 29 Jan 2024 22:23:58 +0000 [thread overview]
Message-ID: <eeb6d178dff61dfebf5a3ce9675486a3271b748c.camel@intel.com> (raw)
In-Reply-To: <fc3fd07a-218d-406c-918b-e7f701968eb0@linux.ibm.com>
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?
next prev parent reply other threads:[~2024-01-29 22:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 18:33 Xi Ruoyao
2023-11-14 9:46 ` Xi Ruoyao
2023-11-14 15:31 ` Peter Zijlstra
2023-11-14 15:40 ` Peter Zijlstra
2023-11-14 16:43 ` Florian Weimer
2023-11-14 20:14 ` Peter Zijlstra
2023-11-15 1:11 ` Edgecombe, Rick P
2023-11-15 8:51 ` Peter Zijlstra
2023-11-15 23:28 ` Edgecombe, Rick P
2023-11-17 1:22 ` Edgecombe, Rick P
2024-01-19 13:56 ` Stefan Liebler
2024-01-22 14:34 ` Stefan Liebler
2024-01-29 22:23 ` Edgecombe, Rick P [this message]
2024-01-30 10:12 ` Stefan Liebler
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=eeb6d178dff61dfebf5a3ce9675486a3271b748c.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=andrealmeid@igalia.com \
--cc=fweimer@redhat.com \
--cc=hca@linux.ibm.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=stli@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=xry111@xry111.site \
/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 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 read-only IMAP folder(s) and NNTP newsgroup(s).