From: Qu Wenruo <wqu@suse.com>
To: Christoph Hellwig <hch@infradead.org>,
Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/4] btrfs: avoid double clean up when submit_one_bio() failed
Date: Mon, 11 Apr 2022 15:35:39 +0800 [thread overview]
Message-ID: <298210b8-2b5d-543a-1e35-7f8888f2b414@suse.com> (raw)
In-Reply-To: <YlPWkL4uYBah7Elo@infradead.org>
On 2022/4/11 15:19, Christoph Hellwig wrote:
> On Mon, Apr 11, 2022 at 03:15:23PM +0800, Qu Wenruo wrote:
>> This patch itself is for backport, thus I didn't change the return type
>> to make backport easier.
>
> Umm, if you don't remove all that buggy error handling code in a
> backport you'll have to fix it. So do the right thing here and just
> get rid of it ASAP including for the backport.
>
I don't think there is much difference by making submit_one_bio() to
always return 0, and backporting the full type change.
For btrfs development, no one will base their code on stable, thus what
they see is the one returning void.
For vendor backports, I have left a comment on why we return 0 manually,
it should be clear enough to solve any future conflicts.
I'll let David to determine the correct way, as small backport + proper
cleanup policy for bug fixes is pretty common here AFAIK.
Thanks,
Qu
next prev parent reply other threads:[~2022-04-11 7:36 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 [this message]
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
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=298210b8-2b5d-543a-1e35-7f8888f2b414@suse.com \
--to=wqu@suse.com \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=stable@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