---
name: "io_uring_prep_rename"
section: "3"
platform: "linux"
package: "liburing"
version: "2.15-1"
release: "Arch Linux 2026-11-01"
platforms: ["linux"]
url: "https://new.carta.tech/io_uring_prep_rename"
---

# io\_uring\_prep\_rename(3)

prepare a renameat request

## NAME

io\_uring\_prep\_renameat - prepare a renameat request

## SYNOPSIS

```
#include <fcntl.h>
#include <stdio.h>
#include <liburing.h>
```

**void io\_uring\_prep\_renameat(struct io\_uring\_sqe \****sqe***,**                             **int** *olddirfd***,**                             **const char \****oldpath***,**                             **int** *newdirfd***,**                             **const char \****newpath***,**                             **unsigned int** *flags***);**

**void io\_uring\_prep\_rename(struct io\_uring\_sqe \****sqe***,**                           **const char \****oldpath***,**                           **const char \****newpath***);**

## DESCRIPTION

The [**io\_uring\_prep\_renameat**(3)](/io_uring_prep_renameat/3.md) function prepares a renameat request. The submission queue entry *sqe* is setup to use the old directory file descriptor pointed to by *olddirfd* and old path pointed to by *oldpath* with the new directory file descriptor pointed to by *newdirfd* and the new path pointed to by *newpath* and using the specified flags in *flags*.

The [**io\_uring\_prep\_rename**(3)](/io_uring_prep_rename/3.md) function prepares a rename request. The submission queue entry *sqe* is setup to use the old path pointed to by *oldpath* with the new path pointed to by *newpath*, both relative to the current working directory and using the specified flags in *flags*.

These functions prepare an async [**renameat2**(2)](/renameat2/2.md) or [**rename**(2)](/rename/2.md) request. If *flags* is zero, then this call is similar to the [**renameat**(2)](/renameat/2.md) system call. See those man pages for details.

## RETURN VALUE

None

## ERRORS

The CQE *res* field will contain the result of the operation. See the related man page for details on possible values. Note that where synchronous system calls will return **-1** on failure and set *errno* to the actual error value, io\_uring never uses *errno*. Instead it returns the negated *errno* directly in the CQE *res* field.

## NOTES

As with any request that passes in data in a struct, that data must remain valid until the request has been successfully submitted. It need not remain valid until completion. Once a request has been submitted, the in-kernel state is stable. Very early kernels (5.4 and earlier) required state to be stable until the completion occurred. Applications can test for this behavior by inspecting the **IORING\_FEAT\_SUBMIT\_STABLE** flag passed back from [**io\_uring\_queue\_init\_params**(3)](/io_uring_queue_init_params/3.md).

## SEE ALSO

[**io\_uring\_get\_sqe**(3)](/io_uring_get_sqe/3.md), [**io\_uring\_submit**(3)](/io_uring_submit/3.md), [**renameat**(2)](/renameat/2.md), [**renameat2**(2)](/renameat2/2.md), [**rename**(2)](/rename/2.md)