util: fall back in rename_noreplace when renameat2 isn't implemented
According to README we only need 3.7, and while it may also make sense to bump that requirement when appropriate, it's trivial to fall back when renameat2 is not available.
This commit is contained in:
parent
9ebdb1e057
commit
715d759905
|
@ -5925,10 +5925,9 @@ int rename_noreplace(int olddirfd, const char *oldpath, int newdirfd, const char
|
|||
if (ret >= 0)
|
||||
return 0;
|
||||
|
||||
/* Even though renameat2() exists since Linux 3.15, btrfs added
|
||||
* support for it later. If it is not implemented, fallback to another
|
||||
* method. */
|
||||
if (errno != EINVAL)
|
||||
/* renameat2() exists since Linux 3.15, btrfs added support for it later.
|
||||
* If it is not implemented, fallback to another method. */
|
||||
if (!IN_SET(errno, EINVAL, ENOSYS))
|
||||
return -errno;
|
||||
|
||||
/* The link()/unlink() fallback does not work on directories. But
|
||||
|
|
Loading…
Reference in a new issue