linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Yossi Goldfill <ygoldfill@radianmemory.com>
Subject: Re: [PATCH] f2fs: fix building on 32-bit architectures
Date: Wed, 13 May 2015 17:23:09 -0700	[thread overview]
Message-ID: <20150514002309.GB68412@jaegeuk-mac02> (raw)
In-Reply-To: <2179770.3R5P5nr1c7@wuerfel>

Hi Arnd,

Thank you for the patch.
Merged and pushed to -next. :)

Thanks,

On Wed, May 13, 2015 at 10:49:58PM +0200, Arnd Bergmann wrote:
> A bug fix to the debug output extended the type of some local
> variables to 64-bit, which now causes the kernel to fail building
> because of missing 64-bit division functions:
> 
> ERROR: "__aeabi_uldivmod" [fs/f2fs/f2fs.ko] undefined!
> 
> In the kernel, we have to use div_u64 or do_div to do this,
> in order to annotate that this is an expensive operation.
> 
> As the function is only called for debug out, we know this
> is not performance critical, so it is safe to use div_u64.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: d1f85bd38db19 ("f2fs: avoid value overflow in showing current status")
> ---
> This patch is required for ARM allmodconfig builds.
> 
> diff --git a/fs/f2fs/debug.c b/fs/f2fs/debug.c
> index efbc83f07305..75176e0dd6c8 100644
> --- a/fs/f2fs/debug.c
> +++ b/fs/f2fs/debug.c
> @@ -113,10 +113,10 @@ static void update_sit_info(struct f2fs_sb_info *sbi)
>  			ndirty++;
>  		}
>  	}
> -	dist = MAIN_SECS(sbi) * hblks_per_sec * hblks_per_sec / 100;
> -	si->bimodal = bimodal / dist;
> +	dist = div_u64(MAIN_SECS(sbi) * hblks_per_sec * hblks_per_sec, 100);
> +	si->bimodal = div_u64(bimodal, dist);
>  	if (si->dirty_count)
> -		si->avg_vblocks = total_vblocks / ndirty;
> +		si->avg_vblocks = div_u64(total_vblocks, ndirty);
>  	else
>  		si->avg_vblocks = 0;
>  }

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

      reply	other threads:[~2015-05-14  0:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 20:49 [PATCH] f2fs: fix building on 32-bit architectures Arnd Bergmann
2015-05-14  0:23 ` Jaegeuk Kim [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=20150514002309.GB68412@jaegeuk-mac02 \
    --to=jaegeuk@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ygoldfill@radianmemory.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).