clone 849923 -1 reassign -1 linux retitle -1 linux: x32 __vdso_clock_gettime falls back to x86-64 syscall thanks
On Tue, Jan 03, 2017 at 02:31:35PM +0100, Thorsten Glaser wrote: > On Mon, 2 Jan 2017, Aurelien Jarno wrote: > > Looking at the issue, it actually appears in __vdso_clock_gettime, which > > is provided by the kernel. This code handle the simple cases (REALTIME, > > MONOTONIC, REALTIME_COARSE and _MONOTONIC_COARSE) and fallbacks to > > the syscall in otherwise, CLOCK_BOOTTIME in the case of sshd. > > Ouch – and the kernel probably thinks it’s getting away with this as > the kernel architecture is amd64… > > Can you please forward this to someone at the kernel side (either Debian > or upstream) who can have a look? In the meantime, I’ll point this issue > out in #debian-x32 on IRC, so the other porters can also look. I've cloned a kernel bug for this with this message. > > On 2017-01-02 17:49, Colin Watson wrote: > > > > sshd's seccomp sandbox is denying a clock_gettime call. But it's more > > Probably a stupid idea, but a short-term stopgap: can we disable seccomp > on x32 for now? That needs: Here's a better stopgap that lets us keep the sandbox enabled: https://anonscm.debian.org/cgit/pkg-ssh/openssh.git/commit/?id=e346421ca6852fbf9f95cf0e764ecc345e5ce21d > • in debian/rules: > +confflags += --host=${DEB_HOST_GNU_TYPE} > This sets $host to x86_64-pc-linux-gnux32 instead of the > auto-detected x86_64-pc-linux-gnu (which is amd64) Unnecessary: the default is --build=x86_64-linux-gnux32, and --host shouldn't be passed when not cross-compiling. You're probably being misled by config.guess's default, but that's already overridden appropriately by dpkg/debhelper. Cheers, -- Colin Watson [cjwat...@debian.org]
