From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/5] xfs: fix sparse warnings about unused interval tree functions
Date: Tue, 2 Apr 2024 20:53:59 -0700 [thread overview]
Message-ID: <20240403035359.GM6390@frogsfrogsfrogs> (raw)
In-Reply-To: <20240402213541.1199959-6-david@fromorbit.com>
On Wed, Apr 03, 2024 at 08:28:32AM +1100, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> Sparse throws warnings about the interval tree functions that are
> defined and then not used in the scrub bitmap code:
>
> fs/xfs/scrub/bitmap.c:57:1: warning: unused function 'xbitmap64_tree_iter_next' [-Wunused-function]
> INTERVAL_TREE_DEFINE(struct xbitmap64_node, bn_rbnode, uint64_t,
> ^
> ./include/linux/interval_tree_generic.h:151:33: note: expanded from macro 'INTERVAL_TREE_DEFINE'
> ITSTATIC ITSTRUCT * \
> ^
> <scratch space>:3:1: note: expanded from here
> xbitmap64_tree_iter_next
> ^
> fs/xfs/scrub/bitmap.c:331:1: warning: unused function 'xbitmap32_tree_iter_next' [-Wunused-function]
> INTERVAL_TREE_DEFINE(struct xbitmap32_node, bn_rbnode, uint32_t,
> ^
> ./include/linux/interval_tree_generic.h:151:33: note: expanded from macro 'INTERVAL_TREE_DEFINE'
> ITSTATIC ITSTRUCT * \
> ^
> <scratch space>:59:1: note: expanded from here
> xbitmap32_tree_iter_next
>
> Fix these by marking the functions created by the interval tree
> creation macro as __maybe_unused to suppress this warning.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
Much better than the hatchet job sent in by the last person...
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/xfs/scrub/bitmap.c | 22 ++++++++++++----------
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/fs/xfs/scrub/bitmap.c b/fs/xfs/scrub/bitmap.c
> index 0cb8d43912a8..7ba35a7a7920 100644
> --- a/fs/xfs/scrub/bitmap.c
> +++ b/fs/xfs/scrub/bitmap.c
> @@ -40,22 +40,23 @@ struct xbitmap64_node {
> * These functions are defined by the INTERVAL_TREE_DEFINE macro, but we'll
> * forward-declare them anyway for clarity.
> */
> -static inline void
> +static inline __maybe_unused void
> xbitmap64_tree_insert(struct xbitmap64_node *node, struct rb_root_cached *root);
>
> -static inline void
> +static inline __maybe_unused void
> xbitmap64_tree_remove(struct xbitmap64_node *node, struct rb_root_cached *root);
>
> -static inline struct xbitmap64_node *
> +static inline __maybe_unused struct xbitmap64_node *
> xbitmap64_tree_iter_first(struct rb_root_cached *root, uint64_t start,
> uint64_t last);
>
> -static inline struct xbitmap64_node *
> +static inline __maybe_unused struct xbitmap64_node *
> xbitmap64_tree_iter_next(struct xbitmap64_node *node, uint64_t start,
> uint64_t last);
>
> INTERVAL_TREE_DEFINE(struct xbitmap64_node, bn_rbnode, uint64_t,
> - __bn_subtree_last, START, LAST, static inline, xbitmap64_tree)
> + __bn_subtree_last, START, LAST, static inline __maybe_unused,
> + xbitmap64_tree)
>
> /* Iterate each interval of a bitmap. Do not change the bitmap. */
> #define for_each_xbitmap64_extent(bn, bitmap) \
> @@ -314,22 +315,23 @@ struct xbitmap32_node {
> * These functions are defined by the INTERVAL_TREE_DEFINE macro, but we'll
> * forward-declare them anyway for clarity.
> */
> -static inline void
> +static inline __maybe_unused void
> xbitmap32_tree_insert(struct xbitmap32_node *node, struct rb_root_cached *root);
>
> -static inline void
> +static inline __maybe_unused void
> xbitmap32_tree_remove(struct xbitmap32_node *node, struct rb_root_cached *root);
>
> -static inline struct xbitmap32_node *
> +static inline __maybe_unused struct xbitmap32_node *
> xbitmap32_tree_iter_first(struct rb_root_cached *root, uint32_t start,
> uint32_t last);
>
> -static inline struct xbitmap32_node *
> +static inline __maybe_unused struct xbitmap32_node *
> xbitmap32_tree_iter_next(struct xbitmap32_node *node, uint32_t start,
> uint32_t last);
>
> INTERVAL_TREE_DEFINE(struct xbitmap32_node, bn_rbnode, uint32_t,
> - __bn_subtree_last, START, LAST, static inline, xbitmap32_tree)
> + __bn_subtree_last, START, LAST, static inline __maybe_unused,
> + xbitmap32_tree)
>
> /* Iterate each interval of a bitmap. Do not change the bitmap. */
> #define for_each_xbitmap32_extent(bn, bitmap) \
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-04-03 3:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 21:28 [PATCH 0/5] xfs: sparse warning fixes Dave Chinner
2024-04-02 21:28 ` [PATCH 1/5] xfs: fix CIL sparse lock context warnings Dave Chinner
2024-04-03 3:53 ` Christoph Hellwig
2024-04-02 21:28 ` [PATCH 2/5] xfs: fix sparse warning in xfs_extent_busy_clear Dave Chinner
2024-04-03 4:04 ` Darrick J. Wong
2024-04-03 4:32 ` Christoph Hellwig
2024-04-02 21:28 ` [PATCH 3/5] xfs: silence sparse warning when checking version number Dave Chinner
2024-04-03 3:57 ` Darrick J. Wong
2024-04-03 4:35 ` Christoph Hellwig
2024-04-02 21:28 ` [PATCH 4/5] xfs: remove unused is_rt_data_fork() function Dave Chinner
2024-04-03 3:54 ` Darrick J. Wong
2024-04-03 4:35 ` Christoph Hellwig
2024-04-02 21:28 ` [PATCH 5/5] xfs: fix sparse warnings about unused interval tree functions Dave Chinner
2024-04-03 3:53 ` Darrick J. Wong [this message]
2024-04-03 4:39 ` 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=20240403035359.GM6390@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=david@fromorbit.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