From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: [GIT PULL] io_uring xattr support
Date: Sun, 22 May 2022 15:26:02 -0600 [thread overview]
Message-ID: <d94a4e55-c4f2-73d8-9e2c-e55ae8436622@kernel.dk> (raw)
Hi Linus,
On top of the core io_uring changes, this pull request includes support
for the xattr variants.
Please pull!
The following changes since commit 155bc9505dbd6613585abbf0be6466f1c21536c4:
io_uring: return an error when cqe is dropped (2022-04-24 18:18:18 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/for-5.19/io_uring-xattr-2022-05-22
for you to fetch changes up to 4ffaa94b9c047fe0e82b1f271554f31f0e2e2867:
io_uring: cleanup error-handling around io_req_complete (2022-04-24 18:29:33 -0600)
----------------------------------------------------------------
for-5.19/io_uring-xattr-2022-05-22
----------------------------------------------------------------
Jens Axboe (1):
io_uring: fix trace for reduced sqe padding
Kanchan Joshi (1):
io_uring: cleanup error-handling around io_req_complete
Stefan Roesch (4):
fs: split off setxattr_copy and do_setxattr 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 | 29 ++++
fs/io_uring.c | 322 ++++++++++++++++++++++++++++++++++++----
fs/xattr.c | 143 ++++++++++++------
include/trace/events/io_uring.h | 9 +-
include/uapi/linux/io_uring.h | 8 +-
5 files changed, 434 insertions(+), 77 deletions(-)
--
Jens Axboe
next reply other threads:[~2022-05-22 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 21:26 Jens Axboe [this message]
2022-05-23 19:41 ` [GIT PULL] io_uring xattr support Linus Torvalds
2022-05-23 19:59 ` Jens Axboe
2022-05-25 18:04 ` Jens Axboe
2022-05-23 20:42 ` pr-tracker-bot
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=d94a4e55-c4f2-73d8-9e2c-e55ae8436622@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).