From: Bill O'Donnell <billodo@redhat.com>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH V2] libxfs: Fix a couple of sparse complaintis
Date: Tue, 17 Jul 2018 12:25:07 -0500 [thread overview]
Message-ID: <20180717172507.GA19265@redhat.com> (raw)
In-Reply-To: <20180717094544.24144-1-cmaiolino@redhat.com>
On Tue, Jul 17, 2018 at 11:45:44AM +0200, Carlos Maiolino wrote:
> No significant changes, just silence a couple of sparse errors.
>
> Using cpu_to_be32(NULLAGINO), the NULLAGINO constant will be encoded in
> BE as a constant, avoiding a BE -> CPU conversion every iteraction of
> the loop, if be32_to_cpu(agi->agi_unlinked[i]) was used instead.
>
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
looks fine.
Reviewed-by: Bill O'Donnell <billodo@redhat.com>
>
> V2:
> Convert NULLAGINO to BE32 instead of converting agi_unlinked[i] to cpu
>
> fs/xfs/libxfs/xfs_ag_resv.h | 2 +-
> fs/xfs/libxfs/xfs_ialloc.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_ag_resv.h b/fs/xfs/libxfs/xfs_ag_resv.h
> index 4619b554ee90..dc953fc84b2f 100644
> --- a/fs/xfs/libxfs/xfs_ag_resv.h
> +++ b/fs/xfs/libxfs/xfs_ag_resv.h
> @@ -28,7 +28,7 @@ xfs_ag_resv_rmapbt_alloc(
> struct xfs_mount *mp,
> xfs_agnumber_t agno)
> {
> - struct xfs_alloc_arg args = {0};
> + struct xfs_alloc_arg args = { NULL };
> struct xfs_perag *pag;
>
> args.len = 1;
> diff --git a/fs/xfs/libxfs/xfs_ialloc.c b/fs/xfs/libxfs/xfs_ialloc.c
> index 0d968e8143aa..9a6bada8a919 100644
> --- a/fs/xfs/libxfs/xfs_ialloc.c
> +++ b/fs/xfs/libxfs/xfs_ialloc.c
> @@ -2539,7 +2539,7 @@ xfs_agi_verify(
> return __this_address;
>
> for (i = 0; i < XFS_AGI_UNLINKED_BUCKETS; i++) {
> - if (agi->agi_unlinked[i] == NULLAGINO)
> + if (agi->agi_unlinked[i] == cpu_to_be32(NULLAGINO))
> continue;
> if (!xfs_verify_ino(mp, be32_to_cpu(agi->agi_unlinked[i])))
> return __this_address;
> --
> 2.14.3
>
> --
> 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:[~2018-07-17 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 9:45 [PATCH V2] libxfs: Fix a couple of sparse complaintis Carlos Maiolino
2018-07-17 17:13 ` Darrick J. Wong
2018-07-17 17:25 ` Bill O'Donnell [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=20180717172507.GA19265@redhat.com \
--to=billodo@redhat.com \
--cc=cmaiolino@redhat.com \
--cc=linux-xfs@vger.kernel.org \
/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).