From: David Sterba <dsterba@suse.cz>
To: Yang Xiuwei <yangxiuwei@kylinos.cn>
Cc: clm@fb.com, dsterba@suse.com, quwenruo.btrfs@gmx.com,
linux-btrfs@vger.kernel.org, io-uring@vger.kernel.org
Subject: Re: [PATCH v3 0/5] btrfs: fix io_uring encoded IO cleanup
Date: Mon, 7 Sep 2026 19:55:12 +0200 [thread overview]
Message-ID: <20260907175512.GZ9053@twin.jikos.cz> (raw)
In-Reply-To: <20260901020921.3261749-1-yangxiuwei@kylinos.cn>
On Tue, Sep 01, 2026 at 10:09:21AM +0800, Yang Xiuwei wrote:
> Hi,
>
> On Wed, Aug 19, 2026, Yang Xiuwei wrote:
> > Fixes for the io_uring ENCODED_READ / ENCODED_WRITE cleanup paths.
>
> Gentle ping on this v3 series.
I did a quick review and added it to linux-next for testing. Sashiko
does not have comments to your patchset but still points out some
existing problems, but this should not block this patchset. I'll have
another look and add it to for-next soonish.
prev parent reply other threads:[~2026-09-07 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 2:54 [PATCH v3 0/5] btrfs: fix io_uring encoded IO cleanup Yang Xiuwei
2026-08-19 2:54 ` [PATCH v3 1/5] btrfs: always return -EIOCBQUEUED after btrfs_uring_read_extent_endio Yang Xiuwei
2026-08-19 2:54 ` [PATCH v3 2/5] btrfs: free iov when btrfs_uring_read_extent fails Yang Xiuwei
2026-08-19 2:54 ` [PATCH v3 3/5] btrfs: unlock inode and extent in caller when uring read extent fails Yang Xiuwei
2026-08-19 2:54 ` [PATCH v3 4/5] btrfs: don't stash uring encoded data across -EAGAIN Yang Xiuwei
2026-08-19 2:54 ` [PATCH v3 5/5] btrfs: drop unused uring encoded IO REISSUE stash helpers Yang Xiuwei
2026-09-01 2:09 ` [PATCH v3 0/5] btrfs: fix io_uring encoded IO cleanup Yang Xiuwei
2026-09-07 17:55 ` David Sterba [this message]
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=20260907175512.GZ9053@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=yangxiuwei@kylinos.cn \
/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