kernel-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Version comparison between the two builds:

 - libseccomp-dev: Both versions built against 2.2.3-2ubuntu1
 - libc6-dev: 2.21-0ubuntu4 → 2.21-0ubuntu5
 - linux-libc-dev: 4.2.0-19.23 → 4.3.0-2.11
 - binutils: 2.25.51.20151113-2ubuntu1 → 2.25.90.20151209-1ubuntu1
 - gcc-5: 5.2.1-24ubuntu3 → 5.3.1-3ubuntu1

This reproduces in a schroot after bind-mounting cgroupfs:

sudo mount -o bind /sys/fs/cgroup/ /var/lib/schroot/mount/schroot-
xenial-i386-systemd/sys/fs/cgroup/

I bisected the above toolchain packages, and when building systemd
against linux-libc-dev 4.2.0-16.19 it works again.

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1526358

Title:
  xenial/i386 regression: nspawn fails with "Failed to add audit seccomp
  rule: Bad address"

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Four days ago, on Dec 10,
  http://autopkgtest.ubuntu.com/packages/s/systemd/xenial/i386/ started
  failing:

  ======================================================================
  FAIL: test_boot (__main__.NspawnTest)
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "/tmp/adt-run.IG1dKn/build.Yzd/systemd-228/debian/tests/boot-and-services", line 204, in test_boot
      self.assertIn(b'fake container started', out)
  AssertionError: b'fake container started' not found in b'Spawning container c1 on /tmp/tmpl04y_tf8/c1.\nPress ^] three times within 1s to kill container.\nFailed to create directory /tmp/tmpl04y_tf8/c1/sys/fs/selinux: Read-only file system\nFailed to create directory /tmp/tmpl04y_tf8/c1/sys/fs/selinux: Read-only file system\nFailed to add audit seccomp rule: Bad address\n'

  This is reproducible in xenial-release, i. e. it already slipped
  through -proposed.

  This can be reproduced easily on a xenial i386 VM:

    sudo apt-get install busybox-static
    mkdir -p /tmp/c/sbin /tmp/c/etc /tmp/c/bin/
    cp /bin/busybox /tmp/c/bin/
    ln -s ../bin/busybox /tmp/c/sbin/init
    ln -s busybox /tmp/c/bin/sh
    cp /etc/os-release /tmp/c/etc
    sudo systemd-nspawn -b -D /tmp/c

  This should normally boot a busybox container; you'll get a few error
  messages as there's no SysV init stuff there, but it should start and
  pressing enter should get you into a shell. But on i386 it fails with

  $   sudo systemd-nspawn -b -D /tmp/c
  Spawning container c on /tmp/c.
  Press ^] three times within 1s to kill container.
  Failed to create directory /tmp/c/sys/fs/selinux: Read-only file system
  Failed to create directory /tmp/c/sys/fs/selinux: Read-only file system
  Failed to add audit seccomp rule: Bad address

  which is what the test case fails on too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1526358/+subscriptions