Issue #10181 has been updated by Nobuyoshi Nakada.


I don't think it is possible to emulate `openat` family by FD in user space.
So adding `rb_cloexec_open2()` is a bad idea, IMHO, not only its name.

----------------------------------------
Feature #10181: New method File.openat()
https://bugs.ruby-lang.org/issues/10181#change-48548

* Author: Technorama Ltd.
* Status: Open
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
The purpose of the openat() function is to enable opening files in directories other than the current working directory without exposure to race conditions. Any part of the path of a file could be changed in parallel to a call to open(), resulting in unspecified behavior. By opening a file descriptor for the target directory and using the openat() function it can be guaranteed that the opened file is located relative to the desired directory.

openat() is part of POSIX.1-2008.

Compatibility:
  Linux kernel >= 2.6.16
  FreeBSD >= 7.0
  OpenBSD >= 5.0
  NetBSD >= 6.1.4
  MacOS/X no

Pull request: https://github.com/ruby/ruby/pull/706



-- 
https://bugs.ruby-lang.org/