From: Brian Foster <bfoster@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfsprogs: fix a couple 32-bit build warnings
Date: Tue, 3 Jan 2017 13:24:51 -0500 [thread overview]
Message-ID: <20170103182451.GA18120@bfoster.bfoster> (raw)
In-Reply-To: <6d40e289-13ef-26fa-24d6-6b8e052d3a76@redhat.com>
On Thu, Dec 22, 2016 at 09:28:50AM -0600, Eric Sandeen wrote:
> on 32-bit builds:
>
> mremap_f can't turn a long long into a pointer, and
> dump_dirent needs proper %llx & a cast for u64 args
> as is done elsewhere.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
Looks Ok to me:
Reviewed-by: Brian Foster <bfoster@redhat.com>
>
> diff --git a/io/mmap.c b/io/mmap.c
> index dc188d0..6f1d330 100644
> --- a/io/mmap.c
> +++ b/io/mmap.c
> @@ -628,8 +628,8 @@ mremap_f(
> switch (c) {
> case 'f':
> flags = MREMAP_FIXED|MREMAP_MAYMOVE;
> - new_addr = (void *)cvtnum(blocksize, sectsize,
> - optarg);
> + new_addr = (void *)(unsigned long)cvtnum(blocksize,
> + sectsize, optarg);
> break;
> case 'm':
> flags = MREMAP_MAYMOVE;
> diff --git a/io/readdir.c b/io/readdir.c
> index 151b72e..b868d1b 100644
> --- a/io/readdir.c
> +++ b/io/readdir.c
> @@ -71,9 +71,10 @@ dump_dirent(
> long long offset,
> struct dirent *dirent)
> {
> - printf("%08llx: d_ino: 0x%08lx", offset, dirent->d_ino);
> + printf("%08llx: d_ino: 0x%08llx", offset,
> + (unsigned long long)dirent->d_ino);
> #ifdef _DIRENT_HAVE_D_OFF
> - printf(" d_off: 0x%08lx", dirent->d_off);
> + printf(" d_off: 0x%08llx", (unsigned long long)dirent->d_off);
> #endif
> #ifdef _DIRENT_HAVE_D_RECLEN
> printf(" d_reclen: 0x%x", dirent->d_reclen);
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-01-03 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 15:28 [PATCH] xfsprogs: fix a couple 32-bit build warnings Eric Sandeen
2017-01-03 18:24 ` Brian Foster [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=20170103182451.GA18120@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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).