From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: fix sign handling problem in xfs_bmbt_diff_two_keys
Date: Thu, 29 Aug 2019 00:23:18 -0700 [thread overview]
Message-ID: <20190829072318.GA18102@infradead.org> (raw)
In-Reply-To: <20190826183803.GQ1037350@magnolia>
On Mon, Aug 26, 2019 at 11:38:03AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> In xfs_bmbt_diff_two_keys, we perform a signed int64_t subtraction with
> two unsigned 64-bit quantities. If the second quantity is actually the
> "maximum" key (all ones) as used in _query_all, the subtraction
> effectively becomes addition of two positive numbers and the function
> returns incorrect results. Fix this with explicit comparisons of the
> unsigned values.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> fs/xfs/libxfs/xfs_bmap_btree.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_bmap_btree.c b/fs/xfs/libxfs/xfs_bmap_btree.c
> index fbb18ba5d905..3c1a805b3775 100644
> --- a/fs/xfs/libxfs/xfs_bmap_btree.c
> +++ b/fs/xfs/libxfs/xfs_bmap_btree.c
> @@ -400,8 +400,20 @@ xfs_bmbt_diff_two_keys(
> union xfs_btree_key *k1,
> union xfs_btree_key *k2)
> {
> - return (int64_t)be64_to_cpu(k1->bmbt.br_startoff) -
> - be64_to_cpu(k2->bmbt.br_startoff);
> + uint64_t a = be64_to_cpu(k1->bmbt.br_startoff);
> + uint64_t b = be64_to_cpu(k2->bmbt.br_startoff);
> +
> + /*
> + * Note: This routine previously casted a and b to int64 and subtracted
> + * them to generate a result. This lead to problems if b was the
> + * "maximum" key value (all ones) being signed incorrectly, hence this
> + * somewhat less efficient version.
Comments documenting what was done previously are a bit of a weird
style, as the reader generally could not care less what there was
previously.
> + */
> + if (a > b)
> + return 1;
> + else if (b > a)
> + return -1;
> + return 0;
Looks good. I wonder if we should have a helper for this through,
as basically any compare function taking 64-bit values will have the
same boilerplate.
I suggest to add a helper like:
/*
* Compare to signed 64-bit values and return an signed 32-bit integer
* value that is 1, -1 or 0 for various compare callbacks.
*/
static inline int cmp_s64(s64 a, s64 b)
{
if (a > b)
return 1;
else if (b > a)
return -1;
return 0;
}
and then the above just comes:
return cmp_s64(be64_to_cpu(k1->bmbt.br_startoff),
be64_to_cpu(k2->bmbt.br_startof));
and we can probably clean up various other places inside (and outside,
but we can leave that for others) as well. I'll cook up a patch if
you feel this is not worth your time.
next prev parent reply other threads:[~2019-08-29 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 18:38 [PATCH] xfs: fix sign handling problem in xfs_bmbt_diff_two_keys Darrick J. Wong
2019-08-29 7:23 ` Christoph Hellwig [this message]
2019-08-29 15:41 ` Darrick J. Wong
2019-08-30 15:30 ` Christoph Hellwig
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=20190829072318.GA18102@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.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