From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Yang Xiuwei <yangxiuwei@kylinos.cn>, Qu Wenruo <wqu@suse.com>
Cc: Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Mark Harmstone <maharmstone@fb.com>,
linux-btrfs@vger.kernel.org, io-uring@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH v2 5/7] btrfs: unlock inode and extent in caller when uring read extent fails
Date: Thu, 6 Aug 2026 19:01:45 +0930 [thread overview]
Message-ID: <adf19dd3-23d9-43cf-bb52-67da37ae31b3@gmx.com> (raw)
In-Reply-To: <20260806093047.1491231-1-yangxiuwei@kylinos.cn>
在 2026/8/6 19:00, Yang Xiuwei 写道:
> Hi Wenruo,
>
> On 2026/8/6 18:40, Qu Wenruo wrote:
>> Why go to that label? We have nothing to release, the old return -ENOMEM
>> works completely fine now.
>
> Right, I overlooked that and kept the v1 goto. Will use return -ENOMEM
> in v3.
In that case, feel free to add my reviewed-by:
Reviewed-by: Qu Wenruo <wqu@suse.com>
>
> Thanks,
> Yang Xiuwei
>
next prev parent reply other threads:[~2026-08-06 9:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 8:50 [PATCH v2 0/7] btrfs: fix io_uring encoded IO cleanup and compat Yang Xiuwei
2026-08-06 8:50 ` [PATCH v2 1/7] btrfs: always return -EIOCBQUEUED after btrfs_uring_read_extent_endio Yang Xiuwei
2026-08-06 8:50 ` [PATCH v2 2/7] btrfs: free iov when btrfs_uring_read_extent fails Yang Xiuwei
2026-08-06 8:50 ` [PATCH v2 3/7] iov_iter: export __import_iovec Yang Xiuwei
2026-08-06 8:50 ` [PATCH v2 4/7] btrfs: use IO_URING_F_COMPAT for uring encoded iovec import Yang Xiuwei
2026-08-06 8:50 ` [PATCH v2 5/7] btrfs: unlock inode and extent in caller when uring read extent fails Yang Xiuwei
2026-08-06 9:10 ` Qu Wenruo
2026-08-06 9:30 ` Yang Xiuwei
2026-08-06 9:31 ` Qu Wenruo [this message]
2026-08-06 8:50 ` [PATCH v2 6/7] btrfs: don't stash uring encoded data across -EAGAIN Yang Xiuwei
2026-08-06 8:50 ` [PATCH v2 7/7] btrfs: drop unused uring encoded IO REISSUE stash helpers Yang Xiuwei
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=adf19dd3-23d9-43cf-bb52-67da37ae31b3@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=maharmstone@fb.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wqu@suse.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