Hello, Just a quick note to say that this also impacts custom init programs using 'env' with the Linux kernel.
e.g. with virtme-ng, after having modified the init script (e.g. in /usr/lib/python3/dist-packages/virtme/guest/virtme-init) to have: #!/usr/bin/env bash instead of #!/bin/bash (what vng dev version is using now: https://github.com/arighi/virtme- ng/pull/480) With that, the virtualised kernel crashes, because the init script returned an error: $ vng -r --no-virtme-ng-init -v (...) Security violation: Requested utility `env` does not match executable name: /usr/libexec/virtiofsd [ 1.344090] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 1.344221] CPU: 0 UID: 0 PID: 1 Comm: virtme-init Not tainted 7.0.0-22-generic #22-Ubuntu PREEMPT(lazy) (Note that virtiofsd is just an "artifact": if I don't use it with --force-9p, it will complain about /usr/bin/qemu-system-x86_64) Switching back to #!/bin/bash, or using gnuenv, or coreutils 0.8.0 binary from upstream fixes the issue. The patch seems to still be present in ubuntu/devel with the future 0.9.0 version: https://git.launchpad.net/ubuntu/+source/rust- coreutils/tree/debian/patches/require-utility-to-be-invoked-at-matching- path.patch?h=ubuntu/devel Note that virtme-ng in the Ubuntu repo is not packaged with virtme-ng- init, so --no-virtme-ng-init is used by default. Is this Ubuntu specific patch still required? Or do we need a workaround in virtme-ng just for Ubuntu? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2137745 Title: Ubuntu patch prevents custom argv[0] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-coreutils/+bug/2137745/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
