From: Stefan Roesch <shr@fb.com>
To: <io-uring@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<kernel-team@fb.com>
Cc: <viro@zeniv.linux.org.uk>, <shr@fb.com>
Subject: [PATCH v2 0/2] io-uring: Make statx api stable
Date: Mon, 14 Feb 2022 16:21:19 -0800 [thread overview]
Message-ID: <20220215002121.2049686-1-shr@fb.com> (raw)
One of the key architectual tenets of io-uring 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.
Patches:
Patch 1: fs: replace const char* parameter in vfs_statx and do_statx with
struct filename
Create filename object outside of do_statx and vfs_statx, so io-uring
can create the filename object during the prepare phase
Patch 2: io-uring: Copy path name during prepare stage for statx
Create and store filename object during prepare phase
There is also a patch for the liburing libray to add a new test case. This
patch makes sure that the api is stable.
"liburing: add test for stable statx api"
The patch has been tested with the liburing test suite and fstests.
Changes:
V2: don't check name in vfs_fstatat
Stefan Roesch (2):
fs: replace const char* parameter in vfs_statx and do_statx with
struct filename
io-uring: Copy path name during prepare stage for statx
fs/internal.h | 4 +++-
fs/io_uring.c | 22 ++++++++++++++++++++--
fs/stat.c | 48 +++++++++++++++++++++++++++++++++++-------------
3 files changed, 58 insertions(+), 16 deletions(-)
base-commit: 754e0b0e35608ed5206d6a67a791563c631cec07
--
2.30.2
next reply other threads:[~2022-02-15 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 0:21 Stefan Roesch [this message]
2022-02-15 0:21 ` [PATCH v2 1/2] fs: replace const char* parameter in vfs_statx and do_statx with struct filename Stefan Roesch
2022-02-15 1:15 ` Al Viro
2022-02-15 18:19 ` Stefan Roesch
2022-02-15 0:21 ` [PATCH v2 2/2] io-uring: Copy path name during prepare stage for statx 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=20220215002121.2049686-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 \
--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 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.