On Thu, 17 Sep 2026 15:27:05 +0530, Disha Goel wrote: > The openat2_test.c code previously hardcoded O_LARGEFILE to 0x8000 on > all architectures other than arm64 (aarch64). > > However, on several architectures this value is different. For example, > on PowerPC (including ppc64le), O_LARGEFILE is defined as 0x10000, > whereas 0x8000 is actually O_NOFOLLOW. > > [...]
Applied to the vfs-7.4.misc branch of the vfs/vfs.git tree. Patches in the vfs-7.4.misc branch should appear in linux-next soon. Please report any outstanding bugs that were missed during review in a new review to the original patch series allowing us to drop it. It's encouraged to provide Acked-bys and Reviewed-bys even though the patch has now been applied. If possible patch trailers will be updated. Note that commit hashes shown below are subject to change due to rebase, trailer updates or similar. If in doubt, please check the listed branch. tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git branch: vfs-7.4.misc [1/2] selftests/filesystems/openat2: fix O_LARGEFILE definitions for non-arm64 architectures https://git.kernel.org/vfs/vfs/c/caddcdb829b2 [2/2] selftests/filesystems/openat2: make /tmp a mountpoint inside private namespace https://git.kernel.org/vfs/vfs/c/26915b466490
