[Bug 1719720] Re: [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127
Steve Langasek
steve.langasek at canonical.com
Wed Sep 27 04:43:01 UTC 2017
'MemoryDenyWriteExecute=yes' is defined in systemd.exec(5) as:
If set, attempts to create memory mappings that are writable and
executable at the same time, or to change existing memory mappings to
become executable, or mapping shared memory segments as executable are
prohibited. Specifically, a system call filter is added that rejects
mmap(2) system calls with both PROT_EXEC and PROT_WRITE set, mprotect(2)
system calls with PROT_EXEC set and shmat(2) system calls with SHM_EXEC
set.
It is surprising that /bin/touch should trip this check. This will
require investigation.
** Package changed: systemd (Ubuntu) => coreutils (Ubuntu)
** Changed in: coreutils (Ubuntu)
Status: New => Triaged
** Changed in: coreutils (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1719720
Title:
[LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with
exit code 127
Status in The Ubuntu-power-systems project:
New
Status in coreutils package in Ubuntu:
Triaged
Bug description:
---Problem Description---
Currently syslog is getting flooded with below log messages ..
Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch /run/run.vpdd
update' failed with exit code 127.
This is on UBuntu 17.10 latest build..
---uname output---
Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = ZZ-L
---Steps to Reproduce---
I have seen these messages logged more often when we do any hotplug operations.. ex. cpu hotplug..
Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.
As suggested in that bug, we did change udev script to create
temporary file under /run and that patch is available in ubuntu 17.10.
Looks like this is udev script issue. If I modify systemd-udevd like
below it works fine.
I've limited udev knowledge. I don't know if you have any other better
solution to this issue.
root at ltc-boston123:/lib/systemd/system# diff -Naurp systemd-udevd.service.org systemd-udevd.service
--- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500
+++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500
@@ -25,7 +25,7 @@ KillMode=mixed
WatchdogSec=3min
TasksMax=infinity
MountFlags=slave
-MemoryDenyWriteExecute=yes
+#MemoryDenyWriteExecute=yes
RestrictRealtime=yes
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
SystemCallArchitectures=native
-Vasant
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1719720/+subscriptions
More information about the foundations-bugs
mailing list