From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 7/9] btrfs: quiten warn if the replace is canceled at finish
Date: Fri, 16 Nov 2018 20:06:36 +0800 [thread overview]
Message-ID: <ae7f7fc1-00de-8caa-a241-35e9dcad36cc@oracle.com> (raw)
In-Reply-To: <20181115153546.GU24115@twin.jikos.cz>
On 11/15/2018 11:35 PM, David Sterba wrote:
> On Sun, Nov 11, 2018 at 10:22:22PM +0800, Anand Jain wrote:
>> When we successfully cancel the replace its scrub returns -ECANCELED,
>> which then passed to btrfs_dev_replace_finishing(), it cleans up based
>> on the scrub returned status and propagates the same -ECANCELED back
>> the parent function. As of now only user can cancel the replace-scrub,
>> so its ok to quieten the warn here.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> fs/btrfs/dev-replace.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/btrfs/dev-replace.c b/fs/btrfs/dev-replace.c
>> index 1dc8e86546db..9031a362921a 100644
>> --- a/fs/btrfs/dev-replace.c
>> +++ b/fs/btrfs/dev-replace.c
>> @@ -497,7 +497,7 @@ static int btrfs_dev_replace_start(struct btrfs_fs_info *fs_info,
>> ret = btrfs_dev_replace_finishing(fs_info, ret);
>> if (ret == -EINPROGRESS) {
>> ret = BTRFS_IOCTL_DEV_REPLACE_RESULT_SCRUB_INPROGRESS;
>> - } else {
>> + } else if (ret != -ECANCELED) {
>> WARN_ON(ret);
>
> While this looks ok, can you please rework it so there are no WARN_ON at
> random places in device-replace, poorly substituting error handling?
>
> The code flow in this case could be changed to make explicit checks for
> the know codes and then a catch-all branch like:
>
> if (ret == -EINPROGRESS) {
> ...
> } else (if == -ESOMETHINGELSE) {
> ...
> } else {
> unknown error, print error and do a proper cleanup
> }
>
As below..
>> }
>>
>> @@ -954,7 +954,7 @@ static int btrfs_dev_replace_kthread(void *data)
>> btrfs_device_get_total_bytes(dev_replace->srcdev),
>> &dev_replace->scrub_progress, 0, 1);
>> ret = btrfs_dev_replace_finishing(fs_info, ret);
>> - WARN_ON(ret);
>> + WARN_ON(ret && ret != -ECANCELED);
>
> This one too, thanks.
btrfs_dev_scrub() can return quite a lot of errno, which is passed
here through the btrfs_dev_replace_finishing(), so it won't be
possible to code them all.
(we use -ECANCELED only in replace and balance).
Thanks, Anand
next prev parent reply other threads:[~2018-11-16 12:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 14:22 [PATCH 0/9 v2] fix replace-start and replace-cancel racing Anand Jain
2018-11-11 14:22 ` [PATCH 1/9] btrfs: mark btrfs_dev_replace_start() as static Anand Jain
2018-11-11 14:22 ` [PATCH 2/9] btrfs: replace go back to suspended if target missing Anand Jain
2018-11-11 14:22 ` [PATCH 3/9] btrfs: replace back to suspend state if EXCL OP is running Anand Jain
2018-11-11 14:22 ` [PATCH 4/9] btrfs: fix UAF due to race between replace start and cancel Anand Jain
2018-11-13 17:24 ` David Sterba
2018-11-14 1:28 ` Anand Jain
2018-11-15 14:00 ` David Sterba
2018-11-15 15:25 ` David Sterba
2018-11-16 6:37 ` Anand Jain
2018-11-14 5:50 ` [PATCH 4/9 v2.1] " Anand Jain
2018-11-11 14:22 ` [PATCH 5/9] btrfs: replace cancel is successful if scrub cancel is successful Anand Jain
2018-11-15 15:27 ` David Sterba
2018-11-16 6:38 ` Anand Jain
2018-11-11 14:22 ` [PATCH 6/9] btrfs: replace's scrub must not be running in replace suspended state Anand Jain
2018-11-11 14:22 ` [PATCH 7/9] btrfs: quiten warn if the replace is canceled at finish Anand Jain
2018-11-15 15:35 ` David Sterba
2018-11-16 12:06 ` Anand Jain [this message]
2018-11-16 18:49 ` David Sterba
2018-11-11 14:22 ` [PATCH 8/9] btrfs: user requsted replace cancel is not an error Anand Jain
2018-11-15 15:31 ` David Sterba
2018-11-16 10:29 ` Anand Jain
2018-11-16 11:05 ` Anand Jain
2018-11-11 14:22 ` [PATCH 9/9] btrfs: add explicit check for replace result no error Anand Jain
2018-11-13 17:33 ` [PATCH 0/9 v2] fix replace-start and replace-cancel racing David Sterba
2018-11-15 15:41 ` David Sterba
2018-11-16 9:32 ` Anand Jain
-- strict thread matches above, loose matches on Subject: below --
2018-11-07 11:43 [PATCH 0/9] " Anand Jain
2018-11-07 11:43 ` [PATCH 7/9] btrfs: quiten warn if the replace is canceled at finish Anand Jain
2018-11-07 12:17 ` Nikolay Borisov
2018-11-08 8:06 ` Anand Jain
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=ae7f7fc1-00de-8caa-a241-35e9dcad36cc@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).