Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1085213 > unrolled thread

Bug#1001558: kore: autopkgtest fail with glibc >= 2.33

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1001558: kore: autopkgtest fail with glibc >= 2.33 Aurelien Jarno <aurel32@debian.org> - 2021-12-12 12:10 +0100

#1085213 — Bug#1001558: kore: autopkgtest fail with glibc >= 2.33

Source: kore
Version: 4.1.0-4
Severity: important
Tags: upstream patch

Dear maintainer,

The kore autopkgtests fails when run on a system with glibc 2.33 installed.
Here is the relevant part of the tests: 

| [parent]: seccomp sandbox enabled
| [parent]: pgsql built-in enabled
| [parent]: tasks built-in enabled
| [parent]: worker [keymgr] (2787) exited with status 31
| [parent]: worker 2000 (pid: 2787) (hdlr: none) gone
| [parent]: worker 2000 died from sandbox violation
| [parent]: keymgr or acme process gone, stopping
| [parent]: server shutting down
| [parent]: waiting for workers to drain and shutdown

The full autopkgtest log is available there:
https://ci.debian.net/data/autopkgtest/unstable/amd64/k/kore/17416478/log.gz

The problem is that following glibc commit 6073bae64ccf ("linux:
Disentangle fstatat from fxstatat") that went into release 2.33, calls
to fstat can end-up calling the newfstatat syscall.

I submitted the following patch to add this syscall to the keymgr
seccomp rules:
https://git.kore.io/kore/commit/a641c293017e22679a43699670d934ffe833add2

Regards,
Aurelien

[toc] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web