public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Stefan Roesch <shr@fb.com>
Cc: io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	kernel-team@fb.com, viro@zeniv.linux.org.uk, rostedt@goodmis.org,
	m.szyprowski@samsung.com
Subject: Re: [PATCH v4 1/1] io-uring: Make statx API stable
Date: Sat, 26 Feb 2022 12:01:16 -0800	[thread overview]
Message-ID: <20220226200116.mlirionrzr3ujvx4@garbanzo> (raw)
In-Reply-To: <20220225185326.1373304-2-shr@fb.com>

On Fri, Feb 25, 2022 at 10:53:26AM -0800, Stefan Roesch wrote:
> One of the key architectual tenets is to keep the parameters for
> io-uring stable. After the call has been submitted, its value can
> be changed. Unfortunaltely this is not the case for the current statx
> implementation.
> 
> IO-Uring change:
> This changes replaces the const char * filename pointer in the io_statx
> structure with a struct filename *. In addition it also creates the
> filename object during the prepare phase.
> 
> With this change, the opcode also needs to invoke cleanup, so the
> filename object gets freed after processing the request.
> 
> fs change:
> This replaces the const char* __user filename parameter in the two
> functions do_statx and vfs_statx with a struct filename *. In addition
> to be able to correctly construct a filename object a new helper
> function getname_statx_lookup_flags is introduced. The function makes
> sure that do_statx and vfs_statx is invoked with the correct lookup flags.
> 
> Signed-off-by: Stefan Roesch <shr@fb.com>

At least it doesn't break my KVM boots anymore:

Tested-by: Luis Chamberlain <mcgrof@kernel.org>

  Luis

  reply	other threads:[~2022-02-26 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 18:53 [PATCH v4 0/1] io-uring: Make statx api stable Stefan Roesch
2022-02-25 18:53 ` [PATCH v4 1/1] io-uring: Make statx API stable Stefan Roesch
2022-02-26 20:01   ` Luis Chamberlain [this message]
2022-02-25 20:30 ` [PATCH v4 0/1] io-uring: Make statx api stable 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 \
    --in-reply-to=20220226200116.mlirionrzr3ujvx4@garbanzo \
    --to=mcgrof@kernel.org \
    --cc=io-uring@vger.kernel.org \
    --cc=kernel-team@fb.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=rostedt@goodmis.org \
    --cc=shr@fb.com \
    --cc=viro@zeniv.linux.org.uk \
    /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