[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231115085102.GY3818@noisy.programming.kicks-ass.net>
Date: Wed, 15 Nov 2023 09:51:02 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
Cc: "fweimer@...hat.com" <fweimer@...hat.com>,
"xry111@...111.site" <xry111@...111.site>,
"andrealmeid@...lia.com" <andrealmeid@...lia.com>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
"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>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>
Subject: Re: Several tst-robust* tests time out with recent Linux kernel
On Wed, Nov 15, 2023 at 01:11:20AM +0000, Edgecombe, Rick P wrote:
> On Tue, 2023-11-14 at 21:14 +0100, Peter Zijlstra wrote:
> > Urgh, thanks!
> >
> > Confirmed, the below cures things. Although I should probably make
> > that
> > FLAGS_SIZE_32 | FLAGS_SHARED against Linus' tree.
> >
> > Let me go do a proper patch.
>
> I saw these fail on the glibc shadow stack branch today, and I also saw
> this one failing:
> FAIL: nptl/tst-robustpi8
tip/locking/urgent (branch with the fix on) gets me:
root@...-ep:/usr/local/src/glibc# ./build/nptl/tst-robustpi8
running child
verifying locks
running child
verifying locks
running child
verifying locks
running child
verifying locks
running child
verifying locks
root@...-ep:/usr/local/src/glibc#
Which, to my untrained eye, looks like a pass to me.
Powered by blists - more mailing lists