| Summary: | AB-INT: tar failure: got *at() syscall for unknown directory, fd 4 | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Mathieu Dubois-Briand <mathieu.dubois-briand> |
| Component: | oe-core other | Assignee: | Paul Barker <paul> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | amanoj, joaomarcos.costa, rahalirahma23, randy.macleod, richard.purdie, valerian.backeberg, yoann.congal |
| Version: | unspecified | ||
| Target Milestone: | 6.1 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | AB-INT | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
genericx86-64-alt fedora43-vk-1 mathieu/master-next completed at 2026-06-12 08:57:16+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/93/builds/3893/steps/12/logs/stdio We also had similar issue and upgrading pseudo to 1.9.8 solved the issue for us. We use OpenBMC based stack in our org. Yocto version: walnascar. https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-devtools/pseudo/pseudo_git.bb meta-virt ubuntu2604-vk-1 master&master-next completed at 2026-07-11 22:36:04+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/89/builds/3951/steps/13/logs/stdio oe-selftest-armhost ubuntu2404-vk-arm1 master&master-next completed at 2026-07-12 01:47:30+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4325/steps/15/logs/stdio https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/725/steps/12/logs/stdio qemuarm64-musl-ptest ubuntu2604-vk-arm1 --- Exception: subprocess.CalledProcessError: Command 'tar --xattrs --xattrs-include='*' -cf - -S -C /srv/pokybuild/yocto-worker/qemuarm64-musl-ptest/build/build/tmp/work/cortexa57-poky-linux-musl/python3-calver/2025.10.20/deploy-rpms -p . | tar --xattrs --xattrs-include='*' -xf - -C /srv/pokybuild/yocto-worker/qemuarm64-musl-ptest/build/build/tmp/deploy/rpm' returned non-zero exit status 2. Subprocess output: got *at() syscall for unknown directory, fd 4 unknown base path for fd 4, path python3-calver-2025.10.20-r0.cortexa57.rpm couldn't allocate absolute path for 'python3-calver-2025.10.20-r0.cortexa57.rpm'. tar: ./cortexa57/python3-calver-2025.10.20-r0.cortexa57.rpm: Cannot open: Bad address got *at() syscall for unknown directory, fd 4 unknown base path for fd 4, path python3-calver-ptest-2025.10.20-r0.cortexa57.rpm couldn't allocate absolute path for 'python3-calver-ptest-2025.10.20-r0.cortexa57.rpm'. tar: ./cortexa57/python3-calver-ptest-2025.10.20-r0.cortexa57.rpm: Cannot open: Bad address got *at() syscall for unknown directory, fd 4 unknown base path for fd 4, path python3-calver-dev-2025.10.20-r0.cortexa57.rpm couldn't allocate absolute path for 'python3-calver-dev-2025.10.20-r0.cortexa57.rpm'. tar: ./cortexa57/python3-calver-dev-2025.10.20-r0.cortexa57.rpm: Cannot open: Bad address got *at() syscall for unknown directory, fd 4 unknown base path for fd 4, path python3-calver-dbg-2025.10.20-r0.cortexa57.rpm couldn't allocate absolute path for 'python3-calver-dbg-2025.10.20-r0.cortexa57.rpm'. tar: ./cortexa57/python3-calver-dbg-2025.10.20-r0.cortexa57.rpm: Cannot open: Bad address tar: Exiting with failure status due to previous errors The issue seems to be related to this patch in tar (Ubuntu 1.34+dfsg-1ubuntu0.1.22.04.4): https://launchpadlibrarian.net/866842542/tar_1.34+dfsg-1ubuntu0.1.22.04.3_1.34+dfsg-1ubuntu0.1.22.04.4.diff.gz The patch makes changes with regards to tars directory access which fixes a few security vulnerabilities. Save the build directory if / when this happens again. qemux86-world ubuntu2604-vk-2 wrynose completed at 2026-07-18 05:32:48+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/59/builds/4178 qemux86-64-ptest fedora44-vk-1 wrynose completed at 2026-07-18 02:54:35+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4055 (In reply to Randy MacLeod from comment #6) > Save the build directory if / when this happens again. I saved the 2 builds: * ubuntu2604-vk-2:/srv/pokybuild/ycongal/qemux86-world * fedora44-vk-1:/srv/pokybuild/ycongal/qemux86-64-ptest oe-selftest-armhost ubuntu2604-vk-arm1 mathieu/master-next completed at 2026-07-17 13:08:39+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4353/steps/15/logs/stdio oe-selftest-armhost ubuntu2204-vk-arm2 mathieu/master-next completed at 2026-07-17 10:29:42+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4350/steps/15/logs/stdio oe-selftest-armhost ubuntu2204-vk-arm2 mathieu/master-next-tests&mathieu/master-next completed at 2026-07-17 14:38:37+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4355/steps/15/logs/stdio oe-selftest-armhost ubuntu2204-vk-arm2 mathieu/master-next-tests&mathieu/master-next completed at 2026-07-17 18:23:31+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4360/steps/15/logs/stdio oe-selftest-armhost ubuntu2604-vk-arm1 mathieu/master-next completed at 2026-07-17 20:18:10+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4361/steps/15/logs/stdio oe-selftest-armhost ubuntu2404-vk-arm1 mathieu/master-next completed at 2026-07-18 06:55:26+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4366/steps/15/logs/stdio qemuarm64-alt ubuntu2604-vk-1 mathieu/master-next&mathieu/master-next-tests completed at 2026-07-17 19:19:18+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/9/builds/4119/steps/13/logs/stdio |
Is this a pseudo issue? ERROR: libfm-extra-1.3.2-r0 do_package_write_ipk: Error executing a python function in exec_func_python() autogenerated: The stack trace of python calls that resulted in this exception/failure was: File: 'exec_func_python() autogenerated', lineno: 2, function: <module> 0001: *** 0002:sstate_task_postfunc(d) ... Exception: subprocess.CalledProcessError: Command 'tar --xattrs --xattrs-include='*' -cf - -S -C /srv/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/work/core2-64-poky-linux/libfm-extra/1.3.2/deploy-ipks -p . | tar --xattrs --xattrs-include='*' -xf - -C /srv/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/deploy/ipk' returned non-zero exit status 2. Subprocess output: got *at() syscall for unknown directory, fd 4 unknown base path for fd 4, path libfm-extra-src_1.3.2-r0_core2-64.ipk couldn't allocate absolute path for 'libfm-extra-src_1.3.2-r0_core2-64.ipk'. tar: ./core2-64/libfm-extra-src_1.3.2-r0_core2-64.ipk: Cannot open: Bad address got *at() syscall for unknown directory, fd 4 unknown base path for fd 4, path libfm-extra4_1.3.2-r0_core2-64.ipk couldn't allocate absolute path for 'libfm-extra4_1.3.2-r0_core2-64.ipk'. tar: ./core2-64/libfm-extra4_1.3.2-r0_core2-64.ipk: Cannot open: Bad address got *at() syscall for unknown directory, fd 4 unknown base path for fd 4, path libfm-extra-dbg_1.3.2-r0_core2-64.ipk couldn't allocate absolute path for 'libfm-extra-dbg_1.3.2-r0_core2-64.ipk'. tar: ./core2-64/libfm-extra-dbg_1.3.2-r0_core2-64.ipk: Cannot open: Bad address got *at() syscall for unknown directory, fd 4 unknown base path for fd 4, path libfm-extra-dev_1.3.2-r0_core2-64.ipk couldn't allocate absolute path for 'libfm-extra-dev_1.3.2-r0_core2-64.ipk'. tar: ./core2-64/libfm-extra-dev_1.3.2-r0_core2-64.ipk: Cannot open: Bad address tar: Exiting with failure status due to previous errors