From: Damien Le Moal <damien.lemoal@wdc.com>
To: Arnd Bergmann <arnd@arndb.de>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Chao Yu <yuchao0@huawei.com>, Yunlei He <heyunlei@huawei.com>,
	Fan Li <fanofcode.li@samsung.com>,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: fix 32-bit build
Date: Tue, 22 Nov 2016 23:27:00 +0900	[thread overview]
Message-ID: <896398fe-d971-1166-faa8-de2ff005cc70@wdc.com> (raw)
In-Reply-To: <20161122142033.1680054-1-arnd@arndb.de>
Arnd,
> Unfortunately, the sector number is usually a 64-bit number, and
> we probably can't guarantee that bdev_zone_size() returns a
> power-of-two number, so we actually have to do the expensive 64-bit
> operation to get the remainder.
No, the zone size is guaranteed to be a power of 2. See sd_zbc.c in Jens
linux-block tree, branch for-4.10/block. So it is ok to do a
& (bdev_zone_size() - 1) for the remainder.
That was indeed my mistake in this patch. Modulo should not have been
used in the first place. My bad.
> 
> Fixes: 792b84b74b54 ("f2fs: support multiple devices")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>  fs/f2fs/segment.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 634834e5a232..e4c5497aa172 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -685,6 +685,7 @@ static int __f2fs_issue_discard_zone(struct f2fs_sb_info *sbi,
>  {
>  	sector_t nr_sects = SECTOR_FROM_BLOCK(blklen);
>  	sector_t sector;
> +	u32 rem;
>  	int devi = 0;
>  
>  	if (sbi->s_ndevs) {
> @@ -693,7 +694,8 @@ static int __f2fs_issue_discard_zone(struct f2fs_sb_info *sbi,
>  	}
>  	sector = SECTOR_FROM_BLOCK(blkstart);
>  
> -	if (sector % bdev_zone_size(bdev) || nr_sects != bdev_zone_size(bdev)) {
> +	div_u64_rem(sector, bdev_zone_size(bdev), &rem);
> +	if (rem || nr_sects != bdev_zone_size(bdev)) {
>  		f2fs_msg(sbi->sb, KERN_INFO,
>  			"(%d) %s: Unaligned discard attempted (block %x + %x)",
>  			devi, sbi->s_ndevs ? FDEV(devi).path: "",
Thanks !
Best regards.
-- 
Damien Le Moal, Ph.D.
Sr Manager, System Software Research Group,
Western Digital
Damien.LeMoal@hgst.com
Tel: (+81) 0466-98-3593 (Ext. 51-3593)
1 kirihara-cho, Fujisawa, Kanagawa, 252-0888 Japan
www.wdc.com, www.hgst.com
next prev parent reply	other threads:[~2016-11-22 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 14:20 [PATCH] f2fs: fix 32-bit build Arnd Bergmann
2016-11-22 14:27 ` Damien Le Moal [this message]
2016-11-23 18:42 ` Jaegeuk Kim
2016-11-23 21:05   ` Arnd Bergmann
2016-11-23 21:18     ` Jaegeuk Kim
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=896398fe-d971-1166-faa8-de2ff005cc70@wdc.com \
    --to=damien.lemoal@wdc.com \
    --cc=arnd@arndb.de \
    --cc=fanofcode.li@samsung.com \
    --cc=heyunlei@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 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).