All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Chao Yu <yuchao0@huawei.com>, Jaegeuk Kim <jaegeuk@kernel.org>,
	"linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [PATCH 5/5] f2fs-tools: Fix multi-device format with zoned devices
Date: Thu, 21 Mar 2019 09:30:05 +0000	[thread overview]
Message-ID: <BYAPR04MB58163DCF97DC43BB35240FC7E7420@BYAPR04MB5816.namprd04.prod.outlook.com> (raw)
In-Reply-To: 4bbfbf65-a265-5ce2-9e4a-ebd2a88c0feb@huawei.com

On 2019/03/21 17:41, Chao Yu wrote:
> On 2019/3/18 14:39, Damien Le Moal wrote:
>> There is no need to require conventional zones for a zoned block device
>> that is not the first device of a multi-device volume. So exclude the
>> check on the number of conventional zones of the device if the device
>> index is not 0.
>>
>> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
>> ---
>>  lib/libf2fs_zoned.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/libf2fs_zoned.c b/lib/libf2fs_zoned.c
>> index 1a6c5df..2d8244f 100644
>> --- a/lib/libf2fs_zoned.c
>> +++ b/lib/libf2fs_zoned.c
>> @@ -204,7 +204,7 @@ int f2fs_check_zones(int j)
>>  		goto out;
>>  	}
>>  
> 
> How about adding one line comment here to describe why we handle condition
> as below for better readability? I guess using your commit message here is
> enough... :)

Indeed, that would be better. Will add that. Thanks !

> 
>> -	if (dev->zoned_model == F2FS_ZONED_HM &&
>> +	if (j == 0 && dev->zoned_model == F2FS_ZONED_HM &&
>>  			!dev->nr_rnd_zones) {
>>  		ERR_MSG("No conventional zone for super block\n");
>>  		ret = -1;
>>
> 


-- 
Damien Le Moal
Western Digital Research

      reply	other threads:[~2019-03-21  9:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18  6:39 [PATCH 0/5] Zoned block device support improvments Damien Le Moal
2019-03-18  6:39 ` [PATCH 1/5] f2fs-tools: Fix various compilation warnings Damien Le Moal
2019-03-21  6:29   ` Chao Yu
2019-03-18  6:39 ` [PATCH 2/5] f2fs-tools: Add f2fs_io to .gitignore Damien Le Moal
2019-03-21  6:29   ` Chao Yu
2019-03-18  6:39 ` [PATCH 3/5] f2fs-tools: Improve zoned model check Damien Le Moal
2019-03-21  6:32   ` Chao Yu
2019-03-26 18:24   ` Jaegeuk Kim
2019-03-26 22:58     ` Damien Le Moal
2019-03-18  6:39 ` [PATCH 4/5] f2fs-tools: Allow using host-aware devices as regular devices Damien Le Moal
2019-03-21  8:32   ` Chao Yu
2019-03-21  9:29     ` Damien Le Moal
2019-03-21 12:27       ` Chao Yu
2019-03-18  6:39 ` [PATCH 5/5] f2fs-tools: Fix multi-device format with zoned devices Damien Le Moal
2019-03-21  8:41   ` Chao Yu
2019-03-21  9:30     ` Damien Le Moal [this message]

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=BYAPR04MB58163DCF97DC43BB35240FC7E7420@BYAPR04MB5816.namprd04.prod.outlook.com \
    --to=damien.lemoal@wdc.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=yuchao0@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.