* glibc 2.31 status: Machine testing, bug 25396
@ 2020-01-16 14:55 Carlos O'Donell
2020-01-16 15:09 ` Szabolcs Nagy
2020-01-16 15:35 ` Siddhesh Poyarekar
0 siblings, 2 replies; 3+ messages in thread
From: Carlos O'Donell @ 2020-01-16 14:55 UTC (permalink / raw)
To: libc-alpha, Siddhesh Poyarekar, DJ Delorie, H.J. Lu,
Florian Weimer
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: glibc 2.31 status: Machine testing, bug 25396
2020-01-16 14:55 glibc 2.31 status: Machine testing, bug 25396 Carlos O'Donell
@ 2020-01-16 15:09 ` Szabolcs Nagy
2020-01-16 15:35 ` Siddhesh Poyarekar
1 sibling, 0 replies; 3+ messages in thread
From: Szabolcs Nagy @ 2020-01-16 15:09 UTC (permalink / raw)
To: Carlos O'Donell, libc-alpha, Siddhesh Poyarekar, DJ Delorie,
H.J. Lu, Florian Weimer
Cc: nd
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: glibc 2.31 status: Machine testing, bug 25396
2020-01-16 14:55 glibc 2.31 status: Machine testing, bug 25396 Carlos O'Donell
2020-01-16 15:09 ` Szabolcs Nagy
@ 2020-01-16 15:35 ` Siddhesh Poyarekar
1 sibling, 0 replies; 3+ messages in thread
From: Siddhesh Poyarekar @ 2020-01-16 15:35 UTC (permalink / raw)
To: Carlos O'Donell, libc-alpha, DJ Delorie, H.J. Lu,
Florian Weimer
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-01-16 15:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-16 14:55 glibc 2.31 status: Machine testing, bug 25396 Carlos O'Donell
2020-01-16 15:09 ` Szabolcs Nagy
2020-01-16 15:35 ` Siddhesh Poyarekar
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).