[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <822f3a867e5661ce61cea075a00ce04a4e4733f3.camel@intel.com>
Date: Wed, 15 Nov 2023 01:11:20 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "peterz@...radead.org" <peterz@...radead.org>,
"fweimer@...hat.com" <fweimer@...hat.com>
CC: "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 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
It spit out:
mutex_timedlock of 41 in thread 1 failed with 22
child did not die of a signal in round 1
After the fix here I saw the others pass, but still not tst-robustpi8.
Not sure if it is some shadow stack complication. I can try to dig in
tomorrow if the problem doesn't jump out.
Powered by blists - more mailing lists