From: Philip Li <philip.li@intel.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>,
Boqun Feng <boqun.feng@gmail.com>, Gary Guo <gary@garyguo.net>
Subject: Re: rust/helpers/jump_label.c:10:5: sparse: sparse: symbol 'rust_helper_static_key_count' was not declared. Should it be static?
Date: Fri, 29 Nov 2024 08:48:39 +0800 [thread overview]
Message-ID: <Z0kPZwipai5thnw3@rli9-mobl> (raw)
In-Reply-To: <CAH5fLgiH+hu-VA4GTCWRaEBVXoENX36P16EQzDadJptNi=vk8Q@mail.gmail.com>
On Wed, Nov 27, 2024 at 01:07:24PM +0100, Alice Ryhl wrote:
> On Wed, Nov 27, 2024 at 3:38 AM kernel test robot <lkp@intel.com> wrote:
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: b50ecc5aca4d18f1f0c4942f5c797bc85edef144
> > commit: 6e59bcc9c8adec9a5bbedfa95a89946c56c510d9 rust: add static_branch_unlikely for static_key_false
> > date: 3 weeks ago
> > config: um-randconfig-r111-20241126 (https://download.01.org/0day-ci/archive/20241127/202411271011.gFsgMWRv-lkp@intel.com/config)
> > compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 592c0fe55f6d9a811028b5f3507be91458ab2713)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241127/202411271011.gFsgMWRv-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202411271011.gFsgMWRv-lkp@intel.com/
> >
> > sparse warnings: (new ones prefixed by >>)
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > >> rust/helpers/jump_label.c:10:5: sparse: sparse: symbol 'rust_helper_static_key_count' was not declared. Should it be static?
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/mutex.c:11:6: sparse: sparse: symbol 'rust_helper___mutex_init' was not declared. Should it be static?
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/helpers.c: note: in included file:
> > rust/helpers/spinlock.c:16:6: sparse: sparse: context imbalance in 'rust_helper_spin_lock' - wrong count at exit
> > rust/helpers/spinlock.c:21:6: sparse: sparse: context imbalance in 'rust_helper_spin_unlock' - unexpected unlock
> >
> > vim +/rust_helper_static_key_count +10 rust/helpers/jump_label.c
> >
> > 8
> > 9 #ifndef CONFIG_JUMP_LABEL
> > > 10 int rust_helper_static_key_count(struct static_key *key)
>
> Can we turn off sparse warnings for rust/helpers?
Got it, we will ignore the sparse warning for rust/helpers at bot side.
>
> Alice
>
prev parent reply other threads:[~2024-11-29 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 2:37 rust/helpers/jump_label.c:10:5: sparse: sparse: symbol 'rust_helper_static_key_count' was not declared. Should it be static? kernel test robot
2024-11-27 12:07 ` Alice Ryhl
2024-11-29 0:48 ` Philip Li [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=Z0kPZwipai5thnw3@rli9-mobl \
--to=philip.li@intel.com \
--cc=aliceryhl@google.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.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