* Re: glibc: update to 2.31.
2020-02-02 11:21 [PR PATCH] glibc: update to 2.31 voidlinux-github
@ 2020-02-02 15:39 ` voidlinux-github
2020-02-02 17:10 ` voidlinux-github
` (10 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: voidlinux-github @ 2020-02-02 15:39 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
New comment by jnbr on void-packages repository
https://github.com/void-linux/void-packages/pull/18737#issuecomment-581147258
Comment:
```
* System call wrappers for time system calls now use the new time64
system calls when available. On 32-bit targets, these wrappers
attempt to call the new system calls first and fall back to the
older 32-bit time system calls if they are not present. This may
cause issues in environments that cannot handle unsupported system
calls gracefully by returning -ENOSYS. Seccomp sandboxes are
affected by this issue.
```
We should check if this affects chromium or firefox on i686 before merging.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: glibc: update to 2.31.
2020-02-02 11:21 [PR PATCH] glibc: update to 2.31 voidlinux-github
2020-02-02 15:39 ` voidlinux-github
@ 2020-02-02 17:10 ` voidlinux-github
2020-02-02 18:37 ` [NOMERGE] " voidlinux-github
` (9 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: voidlinux-github @ 2020-02-02 17:10 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 221 bytes --]
New comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/pull/18737#issuecomment-581156053
Comment:
I just noticed sshd breaking due to this upgrade, so please hold off merging.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [NOMERGE] glibc: update to 2.31.
2020-02-02 11:21 [PR PATCH] glibc: update to 2.31 voidlinux-github
2020-02-02 15:39 ` voidlinux-github
2020-02-02 17:10 ` voidlinux-github
@ 2020-02-02 18:37 ` voidlinux-github
2020-02-02 18:53 ` voidlinux-github
` (8 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: voidlinux-github @ 2020-02-02 18:37 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]
New comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/pull/18737#issuecomment-581163700
Comment:
> I just noticed sshd breaking due to this upgrade, so please hold off merging.
The sshd is breaking due to its seccomp filter not explicitly allowing the clock_nanosleep and clock_nanosleep_time64 syscalls which are being called due to glibc commit 2e44b10b42 ("sysdeps/clock_nanosleep: Use clock_nanosleep_time64 if avaliable"), so logins fail as the child process is being killed.
This is fixed in openssh upstream with commit b1c82f4b ("seccomp: Allow clock_nanosleep() in sandbox."), which will be part of the next release (see also [1]).
I've backported this for now, but I'm afraid that this means there will be many other packages breaking due to using seccomp sandboxes (note that this is especially valid on 64-bit archs, as glibc is now invoking clock_nanosleep_time64 which has a different syscall nr).
There's also at least one other issue, glibc 2.31 has removed the __glibc_has_include macro (commit bfa864e164 ("Don't use a custom wrapper macro around __has_include (bug 25189)."), and this breaks compilation of sources that include stat.h/statx.h, as gcc does fixincludes on those headers (it will use the gcc fixed-up /usr/lib/gcc/x86_64-unknown-linux-gnu/9.2/include-fixed/bits/statx.h while glibc-2.31 has removed the macro, and fail). See also [2], this seems to be in progress with gcc upstream.
[1] https://bugzilla.mindrot.org/show_bug.cgi?id=3093
[2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91085
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [NOMERGE] glibc: update to 2.31.
2020-02-02 11:21 [PR PATCH] glibc: update to 2.31 voidlinux-github
` (2 preceding siblings ...)
2020-02-02 18:37 ` [NOMERGE] " voidlinux-github
@ 2020-02-02 18:53 ` voidlinux-github
2020-04-30 11:25 ` schnitzeltony
` (7 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: voidlinux-github @ 2020-02-02 18:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 201 bytes --]
New comment by jnbr on void-packages repository
https://github.com/void-linux/void-packages/pull/18737#issuecomment-581165068
Comment:
Besides that, the entries in `common/shlibs` should be updated.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [NOMERGE] glibc: update to 2.31.
2020-02-02 11:21 [PR PATCH] glibc: update to 2.31 voidlinux-github
` (3 preceding siblings ...)
2020-02-02 18:53 ` voidlinux-github
@ 2020-04-30 11:25 ` schnitzeltony
2020-04-30 12:15 ` pullmoll
` (6 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: schnitzeltony @ 2020-04-30 11:25 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
New comment by schnitzeltony on void-packages repository
https://github.com/void-linux/void-packages/pull/18737#issuecomment-621773912
Comment:
Background: Am not using void-linux but it is always a source of inspiration when it comes to trouble with musl. This is an kind of thank you.
For 32bit-targets / glibc >=2.31 / chromium I created a fix [1] - maybe it helps here either
[1] https://github.com/OSSystems/meta-browser/blob/master/recipes-browser/chromium/files/0003-Fix-sandbox-Aw-snap-for-syscalls-403-and-407.patch
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [NOMERGE] glibc: update to 2.31.
2020-02-02 11:21 [PR PATCH] glibc: update to 2.31 voidlinux-github
` (4 preceding siblings ...)
2020-04-30 11:25 ` schnitzeltony
@ 2020-04-30 12:15 ` pullmoll
2020-04-30 12:35 ` ailiop-git
` (5 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: pullmoll @ 2020-04-30 12:15 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 232 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/18737#issuecomment-621795683
Comment:
Hi @schnitzeltony *wink* Thank you for this payback.
P.S.: Long live Space Attack *lol*
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [NOMERGE] glibc: update to 2.31.
2020-02-02 11:21 [PR PATCH] glibc: update to 2.31 voidlinux-github
` (5 preceding siblings ...)
2020-04-30 12:15 ` pullmoll
@ 2020-04-30 12:35 ` ailiop-git
2020-04-30 15:53 ` schnitzeltony
` (4 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: ailiop-git @ 2020-04-30 12:35 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
New comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/pull/18737#issuecomment-621805733
Comment:
thanks, I haven't had the time to look more into this, but one of the issues is that we don't know which other packages this change may break.
One idea could be to scan all binaries on the repo side by dumping their debug symbols and checking for usage of nanosleep/seccomp/prctl, and narrow it down to those pkgs so that we can check them before upgrading.
There's also the second issue mentioned above with the gcc fixincludes and statx headers, that I haven't check yet if it was resolved upstream.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [NOMERGE] glibc: update to 2.31.
2020-02-02 11:21 [PR PATCH] glibc: update to 2.31 voidlinux-github
` (6 preceding siblings ...)
2020-04-30 12:35 ` ailiop-git
@ 2020-04-30 15:53 ` schnitzeltony
2020-09-27 18:01 ` kernle32dll
` (3 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: schnitzeltony @ 2020-04-30 15:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
New comment by schnitzeltony on void-packages repository
https://github.com/void-linux/void-packages/pull/18737#issuecomment-621941398
Comment:
@pullmoll / sorry others - this is completely off-topic but I have to answer:
> P.S.: Long live Space Attack lol
My children and I like Crazy Paint more
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [NOMERGE] glibc: update to 2.31.
2020-02-02 11:21 [PR PATCH] glibc: update to 2.31 voidlinux-github
` (7 preceding siblings ...)
2020-04-30 15:53 ` schnitzeltony
@ 2020-09-27 18:01 ` kernle32dll
2020-12-05 20:42 ` ericonr
` (2 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: kernle32dll @ 2020-09-27 18:01 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 175 bytes --]
New comment by kernle32dll on void-packages repository
https://github.com/void-linux/void-packages/pull/18737#issuecomment-699667323
Comment:
Anyone up to working on this?
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [NOMERGE] glibc: update to 2.31.
2020-02-02 11:21 [PR PATCH] glibc: update to 2.31 voidlinux-github
` (8 preceding siblings ...)
2020-09-27 18:01 ` kernle32dll
@ 2020-12-05 20:42 ` ericonr
2021-01-05 21:34 ` leahneukirchen
2021-01-05 21:34 ` [PR PATCH] [Closed]: " leahneukirchen
11 siblings, 0 replies; 13+ messages in thread
From: ericonr @ 2020-12-05 20:42 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/18737#issuecomment-739413421
Comment:
glibc 2.32 removed SunRPC. We have a couple of packages that from what I can see depend on it, since `libtirpc` was added only on musl. @q66 this is probably of interest to you.
At least:
- xorg-server
- conntrack-tools
- open-vm-tools (doesn't depend on libtirpc on glibc)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [NOMERGE] glibc: update to 2.31.
2020-02-02 11:21 [PR PATCH] glibc: update to 2.31 voidlinux-github
` (9 preceding siblings ...)
2020-12-05 20:42 ` ericonr
@ 2021-01-05 21:34 ` leahneukirchen
2021-01-05 21:34 ` [PR PATCH] [Closed]: " leahneukirchen
11 siblings, 0 replies; 13+ messages in thread
From: leahneukirchen @ 2021-01-05 21:34 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 179 bytes --]
New comment by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/pull/18737#issuecomment-754914451
Comment:
Will be done as part of #24258.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PR PATCH] [Closed]: [NOMERGE] glibc: update to 2.31.
2020-02-02 11:21 [PR PATCH] glibc: update to 2.31 voidlinux-github
` (10 preceding siblings ...)
2021-01-05 21:34 ` leahneukirchen
@ 2021-01-05 21:34 ` leahneukirchen
11 siblings, 0 replies; 13+ messages in thread
From: leahneukirchen @ 2021-01-05 21:34 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 166 bytes --]
There's a closed pull request on the void-packages repository
[NOMERGE] glibc: update to 2.31.
https://github.com/void-linux/void-packages/pull/18737
Description:
^ permalink raw reply [flat|nested] 13+ messages in thread