On 3/11/19 3:41 PM, Lange Norbert wrote:
> Thanks Phillipe,
>
> assume just for a moment that I know little of the issues,
> is there any harm using glibc 2.28 for now, given that I don’t
> run into those deadlocks or could there be some more
> subtile breakage involved?
I don't know. This said,
t: Montag, 11. März 2019 15:19
> To: Lange Norbert ; Jan Kiszka
> ; Xenomai (xenomai@xenomai.org)
>
> Subject: Re: smokey's fork tests hangs with glibc 2.28+ ?
>
> E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY MEASURE, PLEASE
> EXERCISE CAUTION WITH E-MAIL CONTENT AND ANY LINK
t: Montag, 11. März 2019 15:19
> To: Lange Norbert ; Jan Kiszka
> ; Xenomai (xenomai@xenomai.org)
>
> Subject: Re: smokey's fork tests hangs with glibc 2.28+ ?
>
> E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY MEASURE, PLEASE
> EXERCISE CAUTION WITH E-MAIL CONTENT AND ANY LINK
On 3/11/19 3:08 PM, Lange Norbert via Xenomai wrote:
> Thats a rootfs which reproduces the issue. Identical setup, but glibc 2.27
> will not reproduce.
The issue was introduced by [1], which already triggered a bug in the
glibc test suite [2]. In short, calling pthread_atfork() like
Thats a rootfs which reproduces the issue. Identical setup, but glibc 2.27 will
not reproduce.
> -Original Message-
> From: Jan Kiszka
> Sent: Montag, 11. März 2019 14:50
> To: Lange Norbert ; Xenomai
> (xenomai@xenomai.org)
> Subject: Re: smokey's fork tests han
On 11.03.19 14:40, Lange Norbert wrote:
Well, swapping out glibc with 2.27 removes the issue, so it has been introduced
afterwards,
the current buildroot will use 2.28 so you should be able to build yourself a
reproducer that way.
I will also attach a prebuilt rootfs once the clean rebuild is
Well, swapping out glibc with 2.27 removes the issue, so it has been introduced
afterwards,
the current buildroot will use 2.28 so you should be able to build yourself a
reproducer that way.
I will also attach a prebuilt rootfs once the clean rebuild is done.
Unfortunately the smokey suite is
