On Thursday, 11 January 2018 07:13:13 PST Filip Piechocki wrote: > I am running this in a docker container (iamge: > arm32v7/debian:buster). It is done on Asus Tinker board with kernel > version 4.4.71.
4.4 doesn't have the statx() system call, which is the usual source of "can't find file" -- when we ask for the file's status with the statx() system call, under 4.12 with incorrect system call filtering, we get an unexpected error code that leads us to think the file doesn't exist. The two other important filesystem changes that applied to 5.10 (use of renameat2() and O_TMPFILE) should have proper fallback codes. Still, can you try to run outside of a docker container to see if the problem goes away? If it does, can you run your container without system call filtering? Or on a real (non-unionfs) filesystem? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest
