Bug 16327 - Handle new openat2 flags in pseudo
Summary: Handle new openat2 flags in pseudo
Status: NEW
Alias: None
Product: Pseudo
Classification: Yocto Project Subprojects
Component: pseudo (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 6.1
Assignee: Mark Hatle
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2026-06-19 09:17 UTC by Paul Barker
Modified: 2026-06-25 14:40 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Barker 2026-06-19 09:17:12 UTC 
This is very much **not urgent**, but capturing it now that I've seen it.

According to LWN (https://lwn.net/Articles/1078068/), Linux 7.2 will include:

- The openat2() system call supports a new flag called O_EMPTYPATH. It exists for a specific purpose: to allow a process to reopen an O_PATH file descriptor to gain access to the file behind it. With O_EMPTYPATH, an empty path name can be given to openat2(), and the given file descriptor will be used to find the file to (re)open.

- Also new to openat2() is the OPENAT2_REGULAR flag, which will cause an open to fail if the target is not a regular file. The return code in the failure case is a new (to Linux) one: EFTYPE. This flag is meant to be a hardening feature to prevent programs from being manipulated into opening special files.