glibc 2.31 status: Machine testing, bug 25396

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

glibc 2.31 status: Machine testing, bug 25396

Carlos O'Donell-6
Siddhesh,

I expect we'll want Florian and HJ's fix for the NODELETE changes
causing bug 25396 (https://sourceware.org/bugzilla/show_bug.cgi?id=25396)?

Is it OK if the Red Hat glibc team starts doing machine testing
at this stage?

It looks like we have no blockers, and we've been relatively
conservative in terms of changes during the freeze.

--
Cheers,
Carlos.

Reply | Threaded
Open this post in threaded view
|

Re: glibc 2.31 status: Machine testing, bug 25396

Szabolcs Nagy-2
On 16/01/2020 14:55, Carlos O'Donell wrote:

> Siddhesh,
>
> I expect we'll want Florian and HJ's fix for the NODELETE changes
> causing bug 25396 (https://sourceware.org/bugzilla/show_bug.cgi?id=25396)?
>
> Is it OK if the Red Hat glibc team starts doing machine testing
> at this stage?
>
> It looks like we have no blockers, and we've been relatively
> conservative in terms of changes during the freeze.

i think the NEWS talks a lot about public time api
changes, but not so much about the internals: i'd
expect time64 syscalls on new kernels to trigger
existing seccomp whitelists some of which are not
very forgiving (well glibc checks for ENOSYS in the
fallback and seccomp filters normally do EPERM or
kill), so it may affect users.

if you test new glibc with a new kernel on a 32bit
target then i'd look out for this.
Reply | Threaded
Open this post in threaded view
|

Re: glibc 2.31 status: Machine testing, bug 25396

Siddhesh Poyarekar-8
In reply to this post by Carlos O'Donell-6
On 16/01/20 8:25 pm, Carlos O'Donell wrote:
> Siddhesh,
>
> I expect we'll want Florian and HJ's fix for the NODELETE changes
> causing bug 25396 (https://sourceware.org/bugzilla/show_bug.cgi?id=25396)?

This is fine.

> Is it OK if the Red Hat glibc team starts doing machine testing
> at this stage?

Yes please, I was going to wait another couple of days before asking on
list about machine testing progress :)

Siddhesh