Relinking an anonymous (unlinked but open) file

Question

In Unix, it's possible to create a handle to an anonymous file by, e.g., creating and opening it with creat() and then removing the directory link with unlink() - leaving you with a file with an inode and storage but no possible way to re-open it. Such files are often used as temp files (and typically this is what tmpfile() returns to you).

My question: is there any way to re-attach a file like this back into the directory structure? If you could do this it means that you could e.g. implement file writes so that the file appears atomically and fully formed. This appeals to my compulsive neatness. ;)

When poking through the relevant system call functions I expected to find a version of link() called flink() (compare with chmod()/fchmod()) but, at least on Linux this doesn't exist.

Bonus points for telling me how to create the anonymous file without briefly exposing a filename in the disk's directory structure.

Answer 1

A patch for a proposed Linux flink() system call was submitted several years ago, but when Linus stated "there is no way in HELL we can do this securely without major other incursions", that pretty much ended the debate on whether to add this.

Update: As of Linux 3.11, it is now possible to create a file with no directory entry using open() with the new O_TMPFILE flag, and link it into the filesystem once it is fully formed using linkat() on /proc/self/fd/fd with the AT_SYMLINK_FOLLOW flag.

The following example is provided on the open() manual page:

    char path[PATH_MAX];     fd = open("/path/to/dir", O_TMPFILE | O_RDWR, S_IRUSR | S_IWUSR);      /* File I/O on 'fd'... */      snprintf(path, PATH_MAX,  "/proc/self/fd/%d", fd);     linkat(AT_FDCWD, path, AT_FDCWD, "/path/for/file", AT_SYMLINK_FOLLOW); 

Note that linkat() will not allow open files to be re-attached after the last link is removed with unlink().

Answer 2

My question: is there any way to re-attach a file like this back into the directory structure? If you could do this it means that you could e.g. implement file writes so that the file appears atomically and fully formed. This appeals to the my compulsive neatness. ;)

If this is your only goal, you can achieve this in a much simpler and more widely used manner. If you are outputting to a.dat:

1. Open a.dat.part for write.
2. Write your data.
3. Rename a.dat.part to a.dat.

I can understand wanting to be neat, but unlinking a file and relinking it just to be "neat" is kind of silly.

This question on serverfault seems to indicate that this kind of re-linking is unsafe and not supported.