From: Jens Axboe <[email protected]>
To: Stefan Roesch <[email protected]>, [email protected], [email protected]
Subject: Re: [PATCH v2 0/4] liburing: support xattr functions
Date: Wed, 30 Mar 2022 14:47:47 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 3/23/22 9:44 AM, Stefan Roesch wrote:
> Add xattr support and testing to liburing
>
> Patch 1: liburing: update io_uring
> Update io_uring.h with io_uring kernel changes.
>
> Patch 2: liburing: add fsetxattr and setxattr
> Add new helper functions for fsetxattr and setxattr support
> in liburing.
>
> Patch 3: liburing: add fgetxattr and getxattr
> Add new helper functions for fgetxattr and getxattr support
> in liburing.
>
> Patch 4: liburing: add new tests for xattr
> Adds a new test program to test the xattr support.
>
> There are also patches for io_uring and xfstests:
> - Adds xattr support for io_uring
> - Add xattr support to fsstress
Applied in the 'xattr' branch for now, I'll pull it into master
when:
a) The next liburing has been released, and
b) the xattr changes are upstream, targeted 5.19 merge window.
Thanks!
--
Jens Axboe
next prev parent reply other threads:[~2022-03-30 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 15:44 [PATCH v2 0/4] liburing: support xattr functions Stefan Roesch
2022-03-23 15:44 ` [PATCH v2 1/4] liburing: Update io_uring in liburing Stefan Roesch
2022-03-23 15:44 ` [PATCH v2 2/4] liburing: add helper functions for setxattr and fsetxattr Stefan Roesch
2022-03-23 15:44 ` [PATCH v2 3/4] liburing: Add helper functions for fgetxattr and getxattr Stefan Roesch
2022-03-23 15:44 ` [PATCH v2 4/4] liburing: Add new test program to verify xattr support Stefan Roesch
2022-03-30 20:47 ` Jens Axboe [this message]
2022-03-31 12:06 ` [PATCH v2 0/4] liburing: support xattr functions 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 \
[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