public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Stefan Roesch <[email protected]>,
	[email protected], [email protected],
	[email protected]
Subject: Re: [PATCH v2 4/5] io_uring: add fsetxattr and setxattr support
Date: Fri, 3 Dec 2021 03:55:07 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 12/1/21 05:51, Stefan Roesch wrote:
> This adds support to io_uring for the fsetxattr and setxattr API.

io_uring part (4/5 and 5/5) look sane, just one comments below

  
> Signed-off-by: Stefan Roesch <[email protected]>
> ---
>   fs/io_uring.c                 | 174 ++++++++++++++++++++++++++++++++++
>   include/uapi/linux/io_uring.h |   6 +-
>   2 files changed, 179 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 568729677e25..9d977bf243fd 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
[...]
> +static int io_fsetxattr_prep(struct io_kiocb *req,
> +			const struct io_uring_sqe *sqe)
> +{
> +	if (!req->file)
> +		return -EBADF;

No need, io_init_req() will fail the request if it can't get a file.
Same for fgetxattr.


> +
> +	return __io_setxattr_prep(req, sqe, file_mnt_user_ns(req->file));
> +}
> +

-- 
Pavel Begunkov

  reply	other threads:[~2021-12-03  3:55 UTC|newest]

Thread overview: 8+ 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 ` [PATCH v2 3/5] fs: split off do_getxattr from getxattr Stefan Roesch
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 [this message]
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 \
    [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