Your message dated Sun, 14 Sep 2025 21:20:04 +0000
with message-id <[email protected]>
and subject line Bug#1071269: fixed in runc 1.3.0+ds1-1
has caused the Debian Bug report #1071269,
regarding runc: access syscall with F_OK flag fails when used to check a device
char file attached to a container
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1071269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071269
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: runc
X-Debbugs-Cc: [email protected]
Version: 1.0.0~rc93+ds1-5+deb11u3
Severity: important
Tags: upstream
Dear Maintainer,
As reported in https://github.com/ROCm/k8s-device-plugin the version of runc
shipped by Bullseye does not include the following commit:
https://github.com/opencontainers/runc/commit/81707abd33d2ddebcd8ceeb08dfc01bf86d8badd
Packages like Pytorch (ROCm variant) trigger at some point a syscall like
access(/dev/dri/renderDXXX, F_OK)
to check if the GPU char device exists or not, while initializing the GPU
config/settings. In a container runc is responsible to run eBPF checks
when a GPU device is attached, to make sure that the permissions set by
the admin are respected. Due to a bug if the device settings are 'rw' the
eBPF
code will return EPERM even if the user running in the container has all
the rights to access the device. The patch seems really small and it may
save others a long debug time to figure out the root cause of the EPERM
error (that in turn causes the Pytorch's GPU init to fail etc..).
Would it be possible to backport the patch to the current Bullseye version?
As far as I can see it was shipped with 1.0.0~rc94 from upstream, it is very
close to the current runc version in Bullseye.
Thanks in advance!
Luca
-- System Information:
Debian Release: 11.9
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'),
(500, 'oldstable-debug'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-28-amd64 (SMP w/72 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages runc depends on:
ii libc6 2.31-13+deb11u9
ii libseccomp2 2.5.1-1+deb11u1
--- End Message ---
--- Begin Message ---
Source: runc
Source-Version: 1.3.0+ds1-1
Done: Reinhard Tartler <[email protected]>
We believe that the bug you reported is fixed in the latest version of
runc, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Reinhard Tartler <[email protected]> (supplier of updated runc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 14 Sep 2025 16:31:05 -0400
Source: runc
Architecture: source
Version: 1.3.0+ds1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Go Packaging Team <[email protected]>
Changed-By: Reinhard Tartler <[email protected]>
Closes: 1071269 1076814
Changes:
runc (1.3.0+ds1-1) experimental; urgency=medium
.
* Team upload.
* Build against golang-github-cilium-ebpf in experimental
* Contains commit 81707abd33d2ddebcd8ceeb08dfc01bf86d8badd, Closes: #1071269
* Contains commit 77cae9addc0c7c9ef52513b4e46b2e6485e4e469, Closes: #1076814
Checksums-Sha1:
e8ce13334dc74263bfae9614240c71a1e7732e3f 3303 runc_1.3.0+ds1-1.dsc
0b945f2b1e62e3223215c6f9110c55493acf6675 511472 runc_1.3.0+ds1.orig.tar.xz
bd19ba13625df4bdccce415dc7113d85b5cbeb0d 11036 runc_1.3.0+ds1-1.debian.tar.xz
Checksums-Sha256:
659ec18eadbf50f6f20fe5a764fa97be956763741f8fe8384ff8a342153982b9 3303
runc_1.3.0+ds1-1.dsc
5e7a7857e87d9328d0467d419b64637cf4dfd7dc8117f087d8011ce881a055c8 511472
runc_1.3.0+ds1.orig.tar.xz
c29ea29c070694b01d70bb8e81da108980b5af67ecf1b40286630f3f043acb5c 11036
runc_1.3.0+ds1-1.debian.tar.xz
Files:
f296beab01196581977e883157a1c385 3303 admin optional runc_1.3.0+ds1-1.dsc
1e99f75064d276aa11cab694284368cb 511472 admin optional
runc_1.3.0+ds1.orig.tar.xz
ec858a6e2a4e5e3e6cc7f0c0e1739335 11036 admin optional
runc_1.3.0+ds1-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmjHLakUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJsv+hRAAy1HaB+TnZ+FJ9G+asu09jcXca/9z
8d0io5oouzVrFeTP42CKX9Z55f9DB9T2OQKFn90NfJiFVYG8dNKA0hK0fs16G1Fy
SWThaqJpL4LTeMUZTwL+kiaMQRjVjsIQTZ561qJzgSHE4VGW1xwaLL5RUUPQwnsE
sQNzFr+iwlZP34NBCcT5wcjZah8oPPmQYE8ZAh9YO3PvuNDmduF9Vryz/Iyj104q
oOzsfUitmGKsOPIUBxuetChTTL0751alSMRcE3JnElqGhG4BDOdmsZd7u5FS6+K0
Cr8S6p68h0sV3PXbdZPbOddV4QTaxDyVR4Wbi1UZyvnSaAAJmhtvQdULtrwwMo11
8NAyfnZe4Hs5e+GFJxvsyhcdRXbkRyFoGW8O5E0S5zuqaLPNmgEOmIgeR2vSOJun
yIN0OiVO+blLTgXhnk+7WpgwJE9Y5NQuu7lWoiltYv2vas8Wv54rGBbiHDlgHHKJ
dLGH6xX1CAepDSQiYTW5sn74R5hkUtK4zLLZz2i5BjDxvIel9MAhmzDBAg8+TJX+
7HXDkNlSjmCKuWl4x9GBysodNYiQeZdM5XeeEdjeaDXIlsONOUKbF//UbaqrqLQv
KLhK9pDRfJOT4AcECKYNGN5Xh6UgM0XSIfAnSt7LQq0+YQ2CUmQQvM8vheXpxHzR
gxYBoDTZ+vFWArM=
=C5QL
-----END PGP SIGNATURE-----
pgpKwUevhx33s.pgp
Description: PGP signature
--- End Message ---
