On Thu, Sep 12, 2013 at 12:17:31AM +0300, Dan Carpenter wrote:
> There is a '=' vs '==' typo so the ASSERT()s are always true.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
> ---
> Introduced in 21b5c9784b ('xfs: swap extents operations for CRC
> filesystems')
>
> diff --git a/fs/xfs/xfs_bmap_btree.c b/fs/xfs/xfs_bmap_btree.c
> index 531b020..bb8de8e 100644
> --- a/fs/xfs/xfs_bmap_btree.c
> +++ b/fs/xfs/xfs_bmap_btree.c
> @@ -957,9 +957,9 @@ xfs_bmbt_change_owner(
> ASSERT(tp || buffer_list);
> ASSERT(!(tp && buffer_list));
> if (whichfork == XFS_DATA_FORK)
> - ASSERT(ip->i_d.di_format = XFS_DINODE_FMT_BTREE);
> + ASSERT(ip->i_d.di_format == XFS_DINODE_FMT_BTREE);
> else
> - ASSERT(ip->i_d.di_aformat = XFS_DINODE_FMT_BTREE);
> + ASSERT(ip->i_d.di_aformat == XFS_DINODE_FMT_BTREE);
>
Eek!
Well, actually, it's harmless, because the only callers of that
function do so after checking that ip->i_d.di_format ==
XFS_DINODE_FMT_BTREE.
So, the fix is definitely needed, but it's not as bad as it looks.
Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>
Thanks, Dan.
Cheers,
Dave.
--
Dave Chinner
dchinner@xxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
