From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 6/9] btrfs: replace's scrub must not be running in replace suspended state
Date: Thu, 8 Nov 2018 17:07:31 +0800 [thread overview]
Message-ID: <bc1d0ae6-6b98-4e23-d9a3-06d2e0a25602@oracle.com> (raw)
In-Reply-To: <96737468-b987-d2cb-c2ad-6217ac834393@suse.com>
On 11/08/2018 04:52 PM, Nikolay Borisov wrote:
>
>
> On 8.11.18 г. 10:33 ч., Anand Jain wrote:
>>
>>
>> On 11/07/2018 08:19 PM, Nikolay Borisov wrote:
>>>
>>>
>>> On 7.11.18 г. 13:43 ч., Anand Jain wrote:
>>>> + /* scrub for replace must not be running in suspended state */
>>>> + if (btrfs_scrub_cancel(fs_info) != -ENOTCONN)
>>>> + ASSERT(0);
>>>
>>> ASSERT(btrfs_scrub_cancel(fs_info) == -ENOTCONN)
>>>
>>
>> There will be substantial difference in code when compiled with and
>> without CONFIG_BTRFS_ASSERT [1]. That is, btrfs_scrub_cancel(fs_info)
>> won't be run at all, I would like to keep it as it is.
>
> Fair point, in that case do:
>
> ret = btrfs_scrub_cancel(fs_info);
> ASSERT(ret != -ENOTCONN);
Fixed.
Thanks, Anand
> result
>
>
>>
>> [1]
>> ------
>> ./fs/btrfs/ctree.h
>> #ifdef CONFIG_BTRFS_ASSERT
>>
>> __cold
>> static inline void assfail(const char *expr, const char *file, int line)
>> {
>> pr_err("assertion failed: %s, file: %s, line: %d\n",
>> expr, file, line);
>> BUG();
>> }
>>
>> #define ASSERT(expr) \
>> (likely(expr) ? (void)0 : assfail(#expr, __FILE__, __LINE__))
>> #else
>> #define ASSERT(expr) ((void)0)
>> #endif
>> -------
>>
>> Thanks, Anand
>>
>>
next prev parent reply other threads:[~2018-11-08 9:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 11:43 [PATCH 0/9] fix replace-start and replace-cancel racing Anand Jain
2018-11-07 11:43 ` [PATCH 1/9] btrfs: mark btrfs_dev_replace_start() as static Anand Jain
2018-11-07 12:04 ` Nikolay Borisov
2018-11-07 11:43 ` [PATCH 2/9] btrfs: replace go back to suspended if target missing Anand Jain
2018-11-07 12:35 ` Nikolay Borisov
2018-11-11 14:00 ` Anand Jain
2018-11-07 11:43 ` [PATCH 3/9] btrfs: replace back to suspend state if EXCL OP is running Anand Jain
2018-11-07 11:43 ` [PATCH 4/9] btrfs: fix UAF due to race between replace start and cancel Anand Jain
2018-11-07 11:43 ` [PATCH 5/9] btrfs: replace cancel is successful if scrub cancel is successful Anand Jain
2018-11-07 12:25 ` Nikolay Borisov
2018-11-07 12:26 ` Nikolay Borisov
2018-11-07 11:43 ` [PATCH 6/9] btrfs: replace's scrub must not be running in replace suspended state Anand Jain
2018-11-07 12:19 ` Nikolay Borisov
2018-11-08 8:33 ` Anand Jain
2018-11-08 8:52 ` Nikolay Borisov
2018-11-08 9:07 ` Anand Jain [this message]
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
2018-11-07 11:43 ` [PATCH 8/9] btrfs: user requsted replace cancel is not an error Anand Jain
2018-11-07 11:43 ` [PATCH 9/9] btrfs: add explicit check for replace result no error Anand Jain
2018-11-07 12:15 ` Nikolay Borisov
2018-11-08 7:26 ` Anand Jain
-- strict thread matches above, loose matches on Subject: below --
2018-11-11 14:22 [PATCH 0/9 v2] fix replace-start and replace-cancel racing Anand Jain
2018-11-11 14:22 ` [PATCH 6/9] btrfs: replace's scrub must not be running in replace suspended state 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=bc1d0ae6-6b98-4e23-d9a3-06d2e0a25602@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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).