From: Anand Jain <anand.jain@oracle.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.cz
Subject: Re: [PATCH 4/4] btrfs: cleanup barrier_all_devices() to check dev stat flush error
Date: Tue, 14 Mar 2017 00:21:12 +0800 [thread overview]
Message-ID: <1d9050d3-64c0-76d9-26e7-e06c278797da@oracle.com> (raw)
In-Reply-To: <c425830d-9c70-f795-9ad6-05d6ea62a0dc@cn.fujitsu.com>
Thanks for the review..
On 03/13/2017 05:05 PM, Qu Wenruo wrote:
>
>
> At 03/13/2017 03:42 PM, Anand Jain wrote:
>> The objective of this patch is to cleanup barrier_all_devices()
>> so that the error checking is in a separate loop independent of
>> of the loop which submits and waits on the device flush requests.
>
> The idea itself is quite good, and we do need it.
Thanks.
>>
>> By doing this it helps to further develop patches which would tune
>> the error-actions as needed.
>>
>> Here functions such as btrfs_dev_stats_dirty() couldn't be used
>> because it doesn't monitor the flush errors BTRFS_DEV_STAT_FLUSH_ERRS.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> fs/btrfs/disk-io.c | 96
>> +++++++++++++++++++++++++++++++++++++++++++++++-------
>> 1 file changed, 85 insertions(+), 11 deletions(-)
>>
>> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
>> index 5719e036048b..12531a5b14ff 100644
>> --- a/fs/btrfs/disk-io.c
>> +++ b/fs/btrfs/disk-io.c
>> @@ -3566,6 +3566,76 @@ static int write_dev_flush(struct btrfs_device
>> *device, int wait)
>> return 0;
>> }
>>
>> +struct device_checkpoint {
>> + struct list_head list;
>> + struct btrfs_device *device;
>> + int stat_value_checkpoint;
>> +};
>> +
>> +static int add_device_checkpoint(struct list_head *checkpoint,
>
> Could we have another structure instead of list_head to record device
> checkpoints?
> The list_head is never a meaningful structure under most cases.
I didn't understand this, there is device_checkpoint and the context
of struct list_head *checkpoint would start and end within
barrier_all_devices().
>
>> + struct btrfs_device *device)
>> +{
>> + struct device_checkpoint *cdev =
>> + kzalloc(sizeof(struct device_checkpoint), GFP_KERNEL);
>> + if (!cdev)
>> + return -ENOMEM;
>
> This means that, we must check return value of add_device_checkpoint(),
> while later code doesn't check it at all.
oh. I will correct this.
>
>> +
>> + list_add(&cdev->list, checkpoint);
>
> And I prefer to do extra check, in case such device is already inserted
> once.
Hmm with the current code its not at all possible, but let me add it.
>> +
>> + cdev->device = device;
>> + cdev->stat_value_checkpoint =
>> + btrfs_dev_stat_read(device, BTRFS_DEV_STAT_FLUSH_ERRS);
>> +
>> + return 0;
>> +}
>> +
>> +static void fini_devices_checkpoint(struct list_head *checkpoint)
>
> Never a fan of the "fini_" naming.
> What about "release_"?
will change it.
>> +{
>> + struct device_checkpoint *cdev;
>> +
>> + while(!list_empty(checkpoint)) {
>> + cdev = list_entry(checkpoint->next,
>> + struct device_checkpoint, list);
>> + list_del(&cdev->list);
>> + kfree(cdev);
>> + }
>> +}
>> +
>> +static int check_stat_flush(struct btrfs_device *dev,
>> + struct list_head *checkpoint)
>> +{
>> + int val;
>> + struct device_checkpoint *cdev;
>> +
>> + list_for_each_entry(cdev, checkpoint, list) {
>> + if (cdev->device == dev) {
>> + val = btrfs_dev_stat_read(dev,
>> + BTRFS_DEV_STAT_FLUSH_ERRS);
>> + if (cdev->stat_value_checkpoint != val)
>> + return 1;
>
> This check implies that BTRFS_DEV_STAT_FLUSH_ERRS will only be modified
> by checkpoint related code.
> Or any other modifier can easily break the check, causing false alert.
I have already checked it, its not possible with the current code,
or do you see if that is possible with the current code ? or Did I
miss something ?
> IIRC that's the reason why I update my previous degraded patch.
>
>
> Personally speaking, I prefer the patchset to take more usage of the
> checkpoint system, or it's a little overkilled for current usage.
Just want to make sure things are done in the right way.
Thanks, Anand
> Thanks,
> Qu
>
>> + }
>> + }
>> + return 0;
>> +}
>> +
>> +static int check_barrier_error(struct btrfs_fs_devices *fsdevs,
>> + struct list_head *checkpoint)
>> +{
>> + int dropouts = 0;
>> + struct btrfs_device *dev;
>> +
>> + list_for_each_entry_rcu(dev, &fsdevs->devices, dev_list) {
>> + if (!dev->bdev || check_stat_flush(dev, checkpoint))
>> + dropouts++;
>> + }
>> +
>> + if (dropouts >
>> + fsdevs->fs_info->num_tolerated_disk_barrier_failures)
>> + return -EIO;
>> +
>> + return 0;
>> +}
>> +
>> /*
>> * send an empty flush down to each device in parallel,
>> * then wait for them
>> @@ -3574,8 +3644,10 @@ static int barrier_all_devices(struct
>> btrfs_fs_info *info)
>> {
>> struct list_head *head;
>> struct btrfs_device *dev;
>> - int dropouts = 0;
>> int ret;
>> + struct list_head checkpoint;
>> +
>> + INIT_LIST_HEAD(&checkpoint);
>>
>> /* send down all the barriers */
>> head = &info->fs_devices->devices;
>> @@ -3587,29 +3659,31 @@ static int barrier_all_devices(struct
>> btrfs_fs_info *info)
>> if (!dev->in_fs_metadata || !dev->writeable)
>> continue;
>>
>> + add_device_checkpoint(&checkpoint, dev);
>> ret = write_dev_flush(dev, 0);
>> - if (ret)
>> + if (ret) {
>> + fini_devices_checkpoint(&checkpoint);
>> return ret;
>> + }
>> }
>>
>> /* wait for all the barriers */
>> list_for_each_entry_rcu(dev, head, dev_list) {
>> if (dev->missing)
>> continue;
>> - if (!dev->bdev) {
>> - dropouts++;
>> + if (!dev->bdev)
>> continue;
>> - }
>> if (!dev->in_fs_metadata || !dev->writeable)
>> continue;
>>
>> - ret = write_dev_flush(dev, 1);
>> - if (ret)
>> - dropouts++;
>> + write_dev_flush(dev, 1);
>> }
>> - if (dropouts > info->num_tolerated_disk_barrier_failures)
>> - return -EIO;
>> - return 0;
>> +
>> + ret = check_barrier_error(info->fs_devices, &checkpoint);
>> +
>> + fini_devices_checkpoint(&checkpoint);
>> +
>> + return ret;
>> }
>>
>> int btrfs_get_num_tolerated_disk_barrier_failures(u64 flags)
>>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-03-13 16:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 7:42 [PATCH 0/4] cleanup barrier_all_devices() Anand Jain
2017-03-13 7:42 ` [PATCH 1/4] btrfs: REQ_PREFLUSH does not use btrfs_end_bio() completion callback Anand Jain
2017-03-28 15:19 ` David Sterba
2017-03-29 10:00 ` Anand Jain
2017-03-30 10:57 ` Anand Jain
2017-03-13 7:42 ` [PATCH 2/4] btrfs: Communicate back ENOMEM when it occurs Anand Jain
2017-03-14 8:49 ` Qu Wenruo
2017-03-28 15:38 ` David Sterba
2017-03-29 10:00 ` Anand Jain
2017-03-13 7:42 ` [PATCH 3/4] btrfs: cleanup barrier_all_devices() unify dev error count Anand Jain
2017-03-14 8:53 ` Qu Wenruo
2017-03-13 7:42 ` [PATCH 4/4] btrfs: cleanup barrier_all_devices() to check dev stat flush error Anand Jain
2017-03-13 9:05 ` Qu Wenruo
2017-03-13 16:21 ` Anand Jain [this message]
2017-03-14 0:28 ` Qu Wenruo
2017-03-14 3:36 ` Anand Jain
2017-03-14 8:26 ` [PATCH V2 " Anand Jain
2017-03-14 8:47 ` Qu Wenruo
2017-03-28 16:19 ` David Sterba
2017-03-29 10:00 ` Anand Jain
2017-03-31 11:36 ` [PATCH 4/4 V2] " Anand Jain
2017-04-05 4:07 ` [PATCH 4/4 V3] " 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=1d9050d3-64c0-76d9-26e7-e06c278797da@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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).