From: Usama Arif <[email protected]>
To: [email protected], [email protected], [email protected]
Cc: [email protected], Usama Arif <[email protected]>
Subject: [PATCH 0/5] io_uring: add opcodes for current working directory
Date: Tue, 31 May 2022 19:41:20 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
This provides consistency between io_uring and the respective I/O syscall
and avoids having the user of liburing specify the cwd in sqe when working
with current working directory, for e.g. the user can directly call with
IORING_OP_RENAME instead of IORING_OP_RENAMEAT and providing AT_FDCWD in
sqe->fd and sqe->len, similar to syscall interface.
This is done for rename, unlink, mkdir, symlink and link in this
patch-series.
The tests for these opcodes in liburing are present at
https://github.com/uarif1/liburing/tree/cwd_opcodes. If the patches are
acceptable, I am happy to create a PR in above for the tests.
Thanks!
Usama Arif (5):
io_uring: add rename opcode for current working directory
io_uring: add unlink opcode for current working directory
io_uring: add mkdir opcode for current working directory
io_uring: add symlink opcode for current working directory
io_uring: add link opcode for current working directory
fs/io_uring.c | 116 ++++++++++++++++++++++++----------
include/uapi/linux/io_uring.h | 5 ++
2 files changed, 89 insertions(+), 32 deletions(-)
--
2.25.1
next reply other threads:[~2022-05-31 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 18:41 Usama Arif [this message]
2022-05-31 18:41 ` [PATCH 1/5] io_uring: add rename opcode for current working directory Usama Arif
2022-05-31 18:41 ` [PATCH 2/5] io_uring: add unlink " Usama Arif
2022-05-31 18:41 ` [PATCH 3/5] io_uring: add mkdir " Usama Arif
2022-05-31 18:41 ` [PATCH 4/5] io_uring: add symlink " Usama Arif
2022-05-31 18:41 ` [PATCH 5/5] io_uring: add link " Usama Arif
2022-05-31 18:58 ` [PATCH 0/5] io_uring: add opcodes " Jens Axboe
2022-05-31 19:18 ` [External] " Usama Arif
2022-05-31 19:22 ` Jens Axboe
2022-05-31 21:35 ` Usama Arif
2022-06-01 2:57 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox