From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: Re: lib/maple_tree.c:330:20: error: unused function 'mte_set_full'
Date: Tue, 3 Sep 2024 12:16:28 -0400 [thread overview]
Message-ID: <fxpibejx4g6tt7ow2l2qmjbd6adquukkszolqgmjvq4oo2s22e@p6wlptkl74px> (raw)
In-Reply-To: <20240831012845.GA2993938@thelio-3990X>
* Nathan Chancellor <nathan@kernel.org> [240830 21:28]:
> On Fri, Aug 30, 2024 at 05:50:15PM -0700, Andrew Morton wrote:
> > On Sat, 31 Aug 2024 07:42:38 +0800 kernel test robot <lkp@intel.com> wrote:
> >
> > > All errors (new ones prefixed by >>):
> > >
> > > >> lib/maple_tree.c:330:20: error: unused function 'mte_set_full' [-Werror,-Wunused-function]
> > > 330 | static inline void mte_set_full(const struct maple_enode *node)
> > > | ^~~~~~~~~~~~
> > > >> lib/maple_tree.c:335:20: error: unused function 'mte_clear_full' [-Werror,-Wunused-function]
> > > 335 | static inline void mte_clear_full(const struct maple_enode *node)
> > > | ^~~~~~~~~~~~~~
> > > 2 errors generated.
> >
> > afaict these have never been used. It's odd that this was just detected.
>
> I don't think it has just now been detected, as these functions have
> been flagged before:
>
> https://lore.kernel.org/20240503160821.GB3960118@thelio-3990X/
>
> > Should we just zap them or is there some reason to retain?
>
> From the above thread, Liam and Matthew seem to want to retain them.
> Perhaps just wrapping them in '#if 0' and a comment that says these will
> eventually see use would be a happy compromise between outright removal
> and doing nothing about this warning?
Besides these functions being static and inline (And thus compiled out),
they are stopping people from trying to use the bit in the address -
which we have had happen.
I am still working on the code to use these on my side, although I have
been held up with other work upstream.
>
> > --- a/lib/maple_tree.c~a
> > +++ a/lib/maple_tree.c
> > @@ -348,21 +348,6 @@ static inline void *mte_safe_root(const
> > return (void *)((unsigned long)node & ~MAPLE_ROOT_NODE);
> > }
> >
> > -static inline void *mte_set_full(const struct maple_enode *node)
> > -{
> > - return (void *)((unsigned long)node & ~MAPLE_ENODE_NULL);
> > -}
> > -
> > -static inline void *mte_clear_full(const struct maple_enode *node)
> > -{
> > - return (void *)((unsigned long)node | MAPLE_ENODE_NULL);
> > -}
> > -
> > -static inline bool mte_has_null(const struct maple_enode *node)
> > -{
> > - return (unsigned long)node & MAPLE_ENODE_NULL;
> > -}
> > -
> > static __always_inline bool ma_is_root(struct maple_node *node)
> > {
> > return ((unsigned long)node->parent & MA_ROOT_PARENT);
> > _
> >
> >
> >
prev parent reply other threads:[~2024-09-03 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 23:42 kernel test robot
2024-08-31 0:50 ` Andrew Morton
2024-08-31 1:28 ` Nathan Chancellor
2024-09-03 16:16 ` Liam R. Howlett [this message]
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=fxpibejx4g6tt7ow2l2qmjbd6adquukkszolqgmjvq4oo2s22e@p6wlptkl74px \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=willy@infradead.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