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 3/5] fs: split off do_getxattr from getxattr
Date: Tue, 30 Nov 2021 21:51:42 -0800 [thread overview]
Message-ID: <20211201055144.3141001-4-shr@fb.com> (raw)
In-Reply-To: <20211201055144.3141001-1-shr@fb.com>
This splits off do_getxattr function from the getxattr
function. This will allow io_uring to call it from its
io worker.
Signed-off-by: Stefan Roesch <shr@fb.com>
---
fs/internal.h | 6 ++++++
fs/xattr.c | 31 ++++++++++++++++++++-----------
2 files changed, 26 insertions(+), 11 deletions(-)
diff --git a/fs/internal.h b/fs/internal.h
index 1b88f29905e6..8326bb5932f0 100644
--- a/fs/internal.h
+++ b/fs/internal.h
@@ -208,6 +208,12 @@ struct xattr_ctx {
int flags;
};
+ssize_t do_getxattr(struct user_namespace *mnt_userns,
+ struct dentry *d,
+ const char *kname,
+ void __user *value,
+ ssize_t size);
+
void *setxattr_setup(struct user_namespace *mnt_userns,
const char __user *name,
struct xattr_ctx *data);
diff --git a/fs/xattr.c b/fs/xattr.c
index 79afea64d7ba..94167a47d7cf 100644
--- a/fs/xattr.c
+++ b/fs/xattr.c
@@ -666,19 +666,12 @@ SYSCALL_DEFINE5(fsetxattr, int, fd, const char __user *, name,
/*
* Extended attribute GET operations
*/
-static ssize_t
-getxattr(struct user_namespace *mnt_userns, struct dentry *d,
- const char __user *name, void __user *value, size_t size)
+ssize_t
+do_getxattr(struct user_namespace *mnt_userns, struct dentry *d,
+ const char *kname, void __user *value, ssize_t size)
{
- ssize_t error;
void *kvalue = NULL;
- char kname[XATTR_NAME_MAX + 1];
-
- error = strncpy_from_user(kname, name, sizeof(kname));
- if (error == 0 || error == sizeof(kname))
- error = -ERANGE;
- if (error < 0)
- return error;
+ ssize_t error;
if (size) {
if (size > XATTR_SIZE_MAX)
@@ -706,6 +699,22 @@ getxattr(struct user_namespace *mnt_userns, struct dentry *d,
return error;
}
+static ssize_t
+getxattr(struct user_namespace *mnt_userns, struct dentry *d,
+ const char __user *name, void __user *value, size_t size)
+{
+ ssize_t error;
+ char kname[XATTR_NAME_MAX + 1];
+
+ error = strncpy_from_user(kname, name, sizeof(kname));
+ if (error == 0 || error == sizeof(kname))
+ error = -ERANGE;
+ if (error < 0)
+ return error;
+
+ return do_getxattr(mnt_userns, d, kname, value, size);
+}
+
static ssize_t path_getxattr(const char __user *pathname,
const char __user *name, void __user *value,
size_t size, unsigned int lookup_flags)
--
2.30.2
next prev parent reply other threads:[~2021-12-01 5:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 5:51 [PATCH v2 0/5] io_uring: add xattr support Stefan Roesch
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 ` Stefan Roesch [this message]
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-4-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.