From: Stefan Roesch <shr@fb.com>
To: <io-uring@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<kernel-team@fb.com>
Cc: <shr@fb.com>
Subject: [PATCH v2 0/5] io_uring: add xattr support
Date: Tue, 30 Nov 2021 21:51:39 -0800 [thread overview]
Message-ID: <20211201055144.3141001-1-shr@fb.com> (raw)
This adds the xattr support to io_uring. The intent is to have a more
complete support for file operations in io_uring.
This change adds support for the following functions to io_uring:
- fgetxattr
- fsetxattr
- getxattr
- setxattr
Patch 1: fs: split off do_user_path_at_empty from user_path_at_empty()
This splits off a new function do_user_path_at_empty from
user_path_at_empty that is based on filename and not on a
user-specified string.
Patch 2: fs: split off setxattr_setup function from setxattr
Split off the setup part of the setxattr function.
Patch 3: fs: split off do_getxattr from getxattr
Split of the do_getxattr part from getxattr. This will
allow it to be invoked it from io_uring.
Patch 4: io_uring: add fsetxattr and setxattr support
This adds new functions to support the fsetxattr and setxattr
functions.
Patch 5: io_uring: add fgetxattr and getxattr support
This adds new functions to support the fgetxattr and getxattr
functions.
There are two additional patches:
liburing: Add support for xattr api's.
This also includes the tests for the new code.
xfstests: Add support for io_uring xattr support.
Signed-off-by: Stefan Roesch <shr@fb.com>
base-commit: c2626d30f312afc341158e07bf088f5a23b4eeeb
---
V2: - split off function do_user_path_empty instead of changing
the function signature of user_path_at
- Fix datatype size problem in do_getxattr
Stefan Roesch (5):
fs: split off do_user_path_at_empty from user_path_at_empty()
fs: split off setxattr_setup function from setxattr
fs: split off do_getxattr from getxattr
io_uring: add fsetxattr and setxattr support
io_uring: add fgetxattr and getxattr support
fs/internal.h | 23 +++
fs/io_uring.c | 327 ++++++++++++++++++++++++++++++++++
fs/namei.c | 10 +-
fs/xattr.c | 106 +++++++----
include/linux/namei.h | 2 +
include/uapi/linux/io_uring.h | 8 +-
6 files changed, 437 insertions(+), 39 deletions(-)
--
2.30.2
next reply other threads:[~2021-12-01 5:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 5:51 Stefan Roesch [this message]
2021-12-01 5:51 ` [PATCH v2 1/5] fs: split off do_user_path_at_empty from user_path_at_empty() Stefan Roesch
2021-12-01 5:51 ` [PATCH v2 2/5] fs: split off setxattr_setup function from setxattr Stefan Roesch
2021-12-01 5:51 ` [PATCH v2 3/5] fs: split off do_getxattr from getxattr Stefan Roesch
2021-12-03 3:41 ` [fs] 196bdb1966: WARNING:at_mm/util.c:#kvmalloc_node kernel test robot
2021-12-03 3:41 ` kernel test robot
2021-12-01 5:51 ` [PATCH v2 4/5] io_uring: add fsetxattr and setxattr support Stefan Roesch
2021-12-03 3:55 ` Pavel Begunkov
2021-12-03 16:41 ` Stefan Roesch
2021-12-01 5:51 ` [PATCH v2 5/5] io_uring: add fgetxattr and getxattr support Stefan Roesch
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 \
--in-reply-to=20211201055144.3141001-1-shr@fb.com \
--to=shr@fb.com \
--cc=io-uring@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.