public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/2] xfs: fix sparse inodes 32-bit compile failure
Date: Tue, 2 Jun 2015 06:52:39 +1000	[thread overview]
Message-ID: <20150601205239.GK24666@dastard> (raw)
In-Reply-To: <1433169194-41808-2-git-send-email-bfoster@redhat.com>

On Mon, Jun 01, 2015 at 10:33:13AM -0400, Brian Foster wrote:
> The kbuild test robot reports the following compilation failure with a
> 32-bit kernel configuration:
> 
> 	fs/built-in.o: In function `xfs_ifree_cluster':
> 	>> xfs_inode.c:(.text+0x17ac84): undefined reference to `__umoddi3'
> 
> This is due to the use of the modulus operator on a 64-bit variable in
> the ASSERT() added as part of the following commit:
> 
> 	xfs: skip unallocated regions of inode chunks in xfs_ifree_cluster()
> 
> This ASSERT() simply checks that the offset of the inode in a sparse
> cluster is appropriately aligned. Since the maximum inode record offset
> is 63 (for a 64 inode record) and the calculated offset here should be
> something less than that, cast the offset value to a 32-bit type before
> the mod to prevent the error.
> 
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Brian Foster <bfoster@redhat.com>
> ---
>  fs/xfs/xfs_inode.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> index 4c054f6..16bd01b 100644
> --- a/fs/xfs/xfs_inode.c
> +++ b/fs/xfs/xfs_inode.c
> @@ -2265,7 +2265,7 @@ xfs_ifree_cluster(
>  		 * a sparse region.
>  		 */
>  		if ((xic->alloc & XFS_INOBT_MASK(inum - xic->first_ino)) == 0) {
> -			ASSERT(((inum - xic->first_ino) %
> +			ASSERT(((int)(inum - xic->first_ino) %
>  				inodes_per_cluster) == 0);

do_mod()

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-06-01 20:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 14:33 [PATCH 0/2] xfs: fix a couple post-merge sparse inode chunks issues Brian Foster
2015-06-01 14:33 ` [PATCH 1/2] xfs: fix sparse inodes 32-bit compile failure Brian Foster
2015-06-01 20:52   ` Dave Chinner [this message]
2015-06-01 21:16   ` [PATCH v2] " Brian Foster
2015-06-01 14:33 ` [PATCH 2/2] xfs: check min blks for random debug mode sparse allocations Brian Foster

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=20150601205239.GK24666@dastard \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=xfs@oss.sgi.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