<feed xmlns='http://www.w3.org/2005/Atom'>
<title>packages/utils/oci-runtime-tools/patches/050-validation-misc_props-run-a-process-the-bundle-contains.patch, branch master</title>
<subtitle>Mirror of packages feed</subtitle>
<id>https://git.openwrt.org/feed/packages/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/feed/packages/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/'/>
<updated>2026-10-20T19:03:57Z</updated>
<entry>
<title>oci-runtime-tools: carry the pending validation fixes</title>
<updated>2026-10-20T19:03:57Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2026-10-20T15:41:30Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/feed/packages/commit/?id=5035328d8dca877ce789d90783f399aba6490402'/>
<id>urn:sha1:5035328d8dca877ce789d90783f399aba6490402</id>
<content type='text'>
Most cgroup tests fail on OpenWrt because the test suite can only read
cgroup v1, and several assertions contradict the runtime-spec or depend
on the test host. Carry the fixes pending upstream in
opencontainers/runtime-tools until they are merged: #812 (cgroup v2
reader), #813 (lifecycle assertions), #814 (pids limit by value), #816
(device rules checked from inside the container), #820 (misc_props
process), #821 (blkio rules on an existing block device) and #822
(RLIMIT_NOFILE read from a child process).

The default seccomp profile of the test configurations lists only the
32-bit time syscalls. On 32-bit targets the Go runtime of runtimetest
uses futex_time64 on Linux 5.1 and later, which the profile denies, so
runtimetest crashes inside every container and most tests report
nothing on i386. Add a patch allowing the time64 variant of every
syscall the profile already allows.

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
</content>
</entry>
</feed>
