https://bugzilla.kernel.org/show_bug.cgi?id=205957 --- Comment #9 from aladjev.andrew@xxxxxxxxx (aladjev.andrew@xxxxxxxxx) --- I've created heavy (but easy) bunch of patches that fixes issue. This is the order of right patches applyment (for gentoo): +----------------------------------------------------------------------------+ | | | amd64 host: +-------------------------------------------------+ | | | | | | linux-headers: kernel | amd64 container: +-----------------------+ | | | gentoo-sources: kernel | | | | | | libseccomp | linux-headers: kernel | arm container (qemu): | | | | go | qemu | | | | | buildah | | linux-headers: kernel | | | | | | glibc | | | | | | | | | | | +-----------------------+ | | | | | | | +-------------------------------------------------+ | | | +----------------------------------------------------------------------------+ You can find full example here https://github.com/andrew-aladev/test-images/tree/master/cross/arm-unknown-linux-gnueabi. Now I am able to emerge several application inside arm container (qemu), so glibc with "getdents64_x32" works perfect. I understand that kernel developers don't like additional syscalls, so they won't accept such kernel patch. But this syscall is the easiest way for me to provide a proof of concept. How to understand these patches? Please read "glibc.patch". Our amd64 kernel is the common kernel for amd64, i386 and arm (via qemu). amd64 is using "getdents64" and arm (without LFS) is using "getdents64_x32". We need to have 2 syscalls simultaneously: "getdents64" and "getdents64_x32" or maybe single syscall with some "x32" flag. I think this will be the most reliable solution. I want to ask glibc and kernel developers to cooperate and find the right solution. This is important not only for arm, it looks like this issue affects any x32 abi. Thank you. -- You are receiving this mail because: You are watching the assignee of the bug.
