From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v2] xfs: fix compiler warnings
Date: Fri, 1 Sep 2017 06:26:23 -0400 [thread overview]
Message-ID: <20170901102622.GB28241@bfoster.bfoster> (raw)
In-Reply-To: <20170831233833.GT3775@magnolia>
On Thu, Aug 31, 2017 at 04:38:33PM -0700, Darrick J. Wong wrote:
> Fix up all the compiler warnings that have crept in.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> fs/xfs/libxfs/xfs_inode_fork.c | 9 +++------
> fs/xfs/xfs_buf_item.c | 2 ++
> fs/xfs/xfs_log_recover.c | 4 ++++
> 3 files changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_inode_fork.c b/fs/xfs/libxfs/xfs_inode_fork.c
> index fb310d0..31840ca 100644
> --- a/fs/xfs/libxfs/xfs_inode_fork.c
> +++ b/fs/xfs/libxfs/xfs_inode_fork.c
> @@ -1499,14 +1499,11 @@ xfs_iext_realloc_indirect(
> xfs_ifork_t *ifp, /* inode fork pointer */
> int new_size) /* new indirection array size */
> {
> - int nlists; /* number of irec's (ex lists) */
> - int size; /* current indirection array size */
> -
> ASSERT(ifp->if_flags & XFS_IFEXTIREC);
> - nlists = ifp->if_real_bytes / XFS_IEXT_BUFSZ;
> - size = nlists * sizeof(xfs_ext_irec_t);
> ASSERT(ifp->if_real_bytes);
> - ASSERT((new_size >= 0) && (new_size != size));
> + ASSERT((new_size >= 0) &&
> + (new_size != ((ifp->if_real_bytes / XFS_IEXT_BUFSZ) *
> + sizeof(xfs_ext_irec_t))));
> if (new_size == 0) {
> xfs_iext_destroy(ifp);
> } else {
> diff --git a/fs/xfs/xfs_buf_item.c b/fs/xfs/xfs_buf_item.c
> index ef2c137..1a7814a 100644
> --- a/fs/xfs/xfs_buf_item.c
> +++ b/fs/xfs/xfs_buf_item.c
> @@ -570,7 +570,9 @@ xfs_buf_item_unlock(
> bool aborted = !!(lip->li_flags & XFS_LI_ABORTED);
> bool hold = !!(bip->bli_flags & XFS_BLI_HOLD);
> bool dirty = !!(bip->bli_flags & XFS_BLI_DIRTY);
> +#ifdef DEBUG
> bool ordered = !!(bip->bli_flags & XFS_BLI_ORDERED);
> +#endif
>
This and the hunk below will break the CONFIG_XFS_WARN build.
Brian
> /* Clear the buffer's association with this transaction. */
> bp->b_transp = NULL;
> diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
> index a362399..04a131c 100644
> --- a/fs/xfs/xfs_log_recover.c
> +++ b/fs/xfs/xfs_log_recover.c
> @@ -4827,12 +4827,16 @@ xlog_recover_process_intents(
> int error = 0;
> struct xfs_ail_cursor cur;
> struct xfs_ail *ailp;
> +#ifdef DEBUG
> xfs_lsn_t last_lsn;
> +#endif
>
> ailp = log->l_ailp;
> spin_lock(&ailp->xa_lock);
> lip = xfs_trans_ail_cursor_first(ailp, &cur, 0);
> +#ifdef DEBUG
> last_lsn = xlog_assign_lsn(log->l_curr_cycle, log->l_curr_block);
> +#endif
> while (lip != NULL) {
> /*
> * We're done when we see something other than an intent.
> --
> 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
next prev parent reply other threads:[~2017-09-01 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 23:38 [PATCH v2] xfs: fix compiler warnings Darrick J. Wong
2017-09-01 0:29 ` Dave Chinner
2017-09-01 8:10 ` Christoph Hellwig
2017-09-01 15:54 ` Darrick J. Wong
2017-09-01 10:26 ` Brian Foster [this message]
2017-09-01 16:19 ` Darrick J. Wong
2017-09-01 16:29 ` Brian Foster
2017-09-01 16:33 ` Darrick J. Wong
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=20170901102622.GB28241@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--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