From: eregontp@... Date: 2017-05-23T17:47:28+00:00 Subject: [ruby-core:81359] [Ruby trunk Feature#13568] File#path for O_TMPFILE fds has no meaning Issue #13568 has been updated by Eregon (Benoit Daloze). I think an exception is the best way to be clear about the problem here, nil or a fake path are most likely to raise exceptions, but later and in a harder to debug way. Moreover, this only happens for O_TMPFILE files, so it seems reasonable to have different behavior. ---------------------------------------- Feature #13568: File#path for O_TMPFILE fds has no meaning https://bugs.ruby-lang.org/issues/13568#change-65055 * Author: sorah (Sorah Fukumori) * Status: Assigned * Priority: Normal * Assignee: sorah (Sorah Fukumori) * Target version: ---------------------------------------- By using File::TMPFILE (O_TMPFILE) allows us to create a file without directory entries. While open(2) with O_TMPFILE don't create a file without directory entries, it still requires a directory name to determine a file system to create a file. Current Ruby implementation holds such directory names in fptr->pathv and retrievable via File#path. But such paths are useless and may raise errors. For example, some code [1] checks File#path availability then when available, it attempts to use the path to open a file in different fd, finally raises Errno::EISDIR. This patch changes File#path (fptr->pathv) not to return String if a fd is opened with O_TMPFILE. [1]: https://github.com/aws/aws-sdk-ruby/blob/v2.9.17/aws-sdk-core/lib/aws-sdk-core/checksums.rb#L15 ---Files-------------------------------- tmpfile-path.patch (1.96 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: