linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] btrfs: fix device order consistency
Date: Thu, 18 Jan 2018 21:55:18 +0800	[thread overview]
Message-ID: <4ce14287-b849-6dee-b62a-bb127cb81448@oracle.com> (raw)
In-Reply-To: <391db1ec-484d-938e-5fa9-a06d52446d21@suse.com>



On 01/18/2018 04:32 PM, Nikolay Borisov wrote:
> 
> 
> On 18.01.2018 04:32, Anand Jain wrote:
>> By maintaining the device order consistency it makes reproducing
>> the problem more consistent. So fix this by having the devices
> 
> Which problem is that ?

  I noticed when trying to reproduce raid1 missed writes issue
  (xfstests test case is coming up). This is good to have as
  such with any device related issue.

Thanks, Anand

>> sorted by some order within the kernel, lets say by devid.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>>   fs/btrfs/volumes.c | 16 ++++++++++++++++
>>   1 file changed, 16 insertions(+)
>>
>> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
>> index d393808071d5..68be58a5b03f 100644
>> --- a/fs/btrfs/volumes.c
>> +++ b/fs/btrfs/volumes.c
>> @@ -27,6 +27,7 @@
>>   #include <linux/raid/pq.h>
>>   #include <linux/semaphore.h>
>>   #include <linux/uuid.h>
>> +#include <linux/list_sort.h>
>>   #include <asm/div64.h>
>>   #include "ctree.h"
>>   #include "extent_map.h"
>> @@ -1108,6 +1109,20 @@ static int __btrfs_open_devices(struct btrfs_fs_devices *fs_devices,
>>   	return ret;
>>   }
>>   
>> +static int device_sort(void *priv, struct list_head *a, struct list_head *b)
>> +{
>> +	struct btrfs_device *dev1, *dev2;
>> +
>> +	dev1 = list_entry(a, struct btrfs_device, dev_list);
>> +	dev2 = list_entry(b, struct btrfs_device, dev_list);
>> +
>> +	if (dev1->devid < dev2->devid)
>> +		return -1;
>> +	else if (dev1->devid > dev2->devid)
>> +		return 1;
>> +	return 0;
>> +}
>> +
>>   int btrfs_open_devices(struct btrfs_fs_devices *fs_devices,
>>   		       fmode_t flags, void *holder)
>>   {
>> @@ -1118,6 +1133,7 @@ int btrfs_open_devices(struct btrfs_fs_devices *fs_devices,
>>   		fs_devices->opened++;
>>   		ret = 0;
>>   	} else {
>> +		list_sort(NULL, &fs_devices->devices, device_sort);
>>   		ret = __btrfs_open_devices(fs_devices, flags, holder);
>>   	}
>>   	mutex_unlock(&uuid_mutex);
>>

  reply	other threads:[~2018-01-18 13:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18  2:32 [PATCH 0/2] fix device orders consistency Anand Jain
2018-01-18  2:32 ` [PATCH 1/2] btrfs: fix device order consistency Anand Jain
2018-01-18  8:32   ` Nikolay Borisov
2018-01-18 13:55     ` Anand Jain [this message]
2018-01-18  2:32 ` [PATCH 2/2] btrfs: fix alloc " 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=4ce14287-b849-6dee-b62a-bb127cb81448@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).