From: Qu Wenruo <wqu@suse.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/4] btrfs: make submit_one_bio() to return void
Date: Mon, 11 Apr 2022 15:20:47 +0800 [thread overview]
Message-ID: <32af072b-ab06-9a89-ad6b-0503106cef94@suse.com> (raw)
In-Reply-To: <YlPWXw+cWtMG0kE8@infradead.org>
On 2022/4/11 15:18, Christoph Hellwig wrote:
> On Mon, Apr 11, 2022 at 02:12:52PM +0800, Qu Wenruo wrote:
>> Since commit "btrfs: avoid double clean up when submit_one_bio()
>> failed", submit_one_bio() will never return any error, as if we hit any
>> error, endio function will be responsible to cleanup the mess.
>>
>> So here we're completely fine to make submit_one_bio() to return void.
>>
>> NOTE: not all bio submission hooks should return void.
>>
>> Hooks for async submission, like btrfs_submit_bio_start_direct_io() or
>> btrfs_submit_bio_start(), they should still return error, so
>> run_one_async_done() can detect the error properly.
>
> This really should go into patch 1.
>
Stable tree won't be happy about the size.
Thanks,
Qu
next prev parent reply other threads:[~2022-04-11 7:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 6:12 [PATCH 0/4] btrfs: vairous bug fixes related to generic/475 failure with subpage cases Qu Wenruo
2022-04-11 6:12 ` [PATCH 1/4] btrfs: avoid double clean up when submit_one_bio() failed Qu Wenruo
2022-04-11 7:14 ` Christoph Hellwig
2022-04-11 7:15 ` Qu Wenruo
2022-04-11 7:19 ` Christoph Hellwig
2022-04-11 7:35 ` Qu Wenruo
2022-04-11 6:12 ` [PATCH 2/4] btrfs: fix the error handling for submit_extent_page() for btrfs_do_readpage() Qu Wenruo
2022-04-11 7:18 ` Christoph Hellwig
2022-04-11 7:31 ` Qu Wenruo
2022-04-11 6:12 ` [PATCH 3/4] btrfs: return correct error number for __extent_writepage_io() Qu Wenruo
2022-04-11 6:12 ` [PATCH 4/4] btrfs: make submit_one_bio() to return void Qu Wenruo
2022-04-11 7:18 ` Christoph Hellwig
2022-04-11 7:20 ` Qu Wenruo [this message]
2022-04-11 12:15 ` Christoph Hellwig
2022-04-11 12:23 ` Greg KH
2022-04-11 12:29 ` Qu Wenruo
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=32af072b-ab06-9a89-ad6b-0503106cef94@suse.com \
--to=wqu@suse.com \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.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