diff options
| author | Disha Goel <disgoel@linux.ibm.com> | 2026-09-17 15:27:05 +0530 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-09-25 13:01:27 +0200 |
| commit | caddcdb829b212595114ce21d2bc48edcb90a260 (patch) | |
| tree | 9542ea0474992aa3df63a6b8c134788cb0027066 /tools/lib/python/kdoc/python_version.py | |
| parent | 6ffe91a84f4434edea8373ce95e3f93cbc3ffa50 (diff) | |
| download | linux-next-caddcdb829b212595114ce21d2bc48edcb90a260.tar.gz linux-next-caddcdb829b212595114ce21d2bc48edcb90a260.zip | |
selftests/filesystems/openat2: fix O_LARGEFILE definitions for non-arm64 architectures
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.
This mismatch caused the flag_validation test case to pass
O_PATH | O_NOFOLLOW instead of O_PATH | O_LARGEFILE. Since
O_PATH | O_NOFOLLOW is a valid and compatible flag combination, the
kernel successfully opened the file instead of failing with -EINVAL,
causing a false test failure on PowerPC.
Fix this by introducing proper architecture-specific definitions for
O_LARGEFILE matching their respective UAPI asm/fcntl.h values.
Signed-off-by: Disha Goel <disgoel@linux.ibm.com>
Link: https://patch.msgid.link/20260917095707.16986-1-disgoel@linux.ibm.com
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions