From: "Darrick J. Wong" <djwong@kernel.org>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: Carlos Maiolino <cem@kernel.org>, Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH 6/6] xfs: refactor xfs_btree_diff_two_ptrs() to take advantage of cmp_int()
Date: Tue, 1 Jul 2025 07:53:19 -0700 [thread overview]
Message-ID: <20250701145319.GB10009@frogsfrogsfrogs> (raw)
In-Reply-To: <20250612102455.63024-7-pchelkin@ispras.ru>
On Thu, Jun 12, 2025 at 01:24:50PM +0300, Fedor Pchelkin wrote:
> Use cmp_int() to yield the result of a three-way-comparison instead of
> performing subtractions with extra casts.
>
> Found by Linux Verification Center (linuxtesting.org).
>
> Signed-off-by: Fedor Pchelkin <pchelkin@ispras.ru>
> ---
> fs/xfs/libxfs/xfs_btree.c | 6 +++---
> fs/xfs/libxfs/xfs_btree.h | 6 +++---
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_btree.c b/fs/xfs/libxfs/xfs_btree.c
> index d3591728998e..9a227b6b3296 100644
> --- a/fs/xfs/libxfs/xfs_btree.c
> +++ b/fs/xfs/libxfs/xfs_btree.c
> @@ -5353,15 +5353,15 @@ xfs_btree_count_blocks(
> }
>
> /* Compare two btree pointers. */
> -int64_t
> +int
> xfs_btree_diff_two_ptrs(
I'm surprised you didn't rename the diff.*ptr functions too -- there's
no inherent meaning in the difference between two pointers, but it is
useful to compare them. Renaming would make the sole callsite much
clearer in purpose:
if (xfs_btree_cmp_two_ptrs(cur, pp, sibling) != 0)
xchk_btree_set_corrupt(bs->sc, cur, level);
Other than that, the logic changes look correct to me.
--D
> struct xfs_btree_cur *cur,
> const union xfs_btree_ptr *a,
> const union xfs_btree_ptr *b)
> {
> if (cur->bc_ops->ptr_len == XFS_BTREE_LONG_PTR_LEN)
> - return (int64_t)be64_to_cpu(a->l) - be64_to_cpu(b->l);
> - return (int64_t)be32_to_cpu(a->s) - be32_to_cpu(b->s);
> + return cmp_int(be64_to_cpu(a->l), be64_to_cpu(b->l));
> + return cmp_int(be32_to_cpu(a->s), be32_to_cpu(b->s));
> }
>
> struct xfs_btree_has_records {
> diff --git a/fs/xfs/libxfs/xfs_btree.h b/fs/xfs/libxfs/xfs_btree.h
> index 1bf20d509ac9..23598f287af5 100644
> --- a/fs/xfs/libxfs/xfs_btree.h
> +++ b/fs/xfs/libxfs/xfs_btree.h
> @@ -519,9 +519,9 @@ struct xfs_btree_block *xfs_btree_get_block(struct xfs_btree_cur *cur,
> int level, struct xfs_buf **bpp);
> bool xfs_btree_ptr_is_null(struct xfs_btree_cur *cur,
> const union xfs_btree_ptr *ptr);
> -int64_t xfs_btree_diff_two_ptrs(struct xfs_btree_cur *cur,
> - const union xfs_btree_ptr *a,
> - const union xfs_btree_ptr *b);
> +int xfs_btree_diff_two_ptrs(struct xfs_btree_cur *cur,
> + const union xfs_btree_ptr *a,
> + const union xfs_btree_ptr *b);
> void xfs_btree_get_sibling(struct xfs_btree_cur *cur,
> struct xfs_btree_block *block,
> union xfs_btree_ptr *ptr, int lr);
> --
> 2.49.0
>
>
next prev parent reply other threads:[~2025-07-01 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 10:24 [PATCH 0/6] xfs: cleanup key comparing routines Fedor Pchelkin
2025-06-12 10:24 ` [PATCH 1/6] xfs: rename diff_two_keys routines Fedor Pchelkin
2025-06-12 10:24 ` [PATCH 2/6] xfs: rename key_diff routines Fedor Pchelkin
2025-06-12 10:24 ` [PATCH 3/6] xfs: refactor cmp_two_keys routines to take advantage of cmp_int() Fedor Pchelkin
2025-06-12 10:24 ` [PATCH 4/6] xfs: refactor cmp_key_with_cur " Fedor Pchelkin
2025-06-12 10:24 ` [PATCH 5/6] xfs: use a proper variable name and type for storing a comparison result Fedor Pchelkin
2025-06-12 10:24 ` [PATCH 6/6] xfs: refactor xfs_btree_diff_two_ptrs() to take advantage of cmp_int() Fedor Pchelkin
2025-07-01 14:53 ` Darrick J. Wong [this message]
2025-07-01 14:53 ` [PATCH 0/6] xfs: cleanup key comparing routines 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=20250701145319.GB10009@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=pchelkin@ispras.ru \
/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
all inboxes | Powered by JetHome®