linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 7728/11071] kernel/rcu/rcuscale.c:301:27: error: 'get_rcu_tasks_gp_kthread' undeclared here (not in a function); did you mean 'get_rcu_tasks_trace_gp_kthread'?
Date: Tue, 20 Jun 2023 16:33:14 -0700	[thread overview]
Message-ID: <2d68cbf4-ef8e-44e9-a6f7-dbd27ca0ac70@paulmck-laptop> (raw)
In-Reply-To: <202306210727.vqY7wkdG-lkp@intel.com>

On Wed, Jun 21, 2023 at 07:28:01AM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   9dbf40840551df336c95ce2a3adbdd25ed53c0ef
> commit: df8fa2f1fc4c20cd300855a11b31ba5565f45ac6 [7728/11071] rcuscale: Measure RCU Tasks Trace grace-period kthread CPU time
> config: microblaze-randconfig-r003-20230620 (https://download.01.org/0day-ci/archive/20230621/202306210727.vqY7wkdG-lkp@intel.com/config)
> compiler: microblaze-linux-gcc (GCC) 12.3.0
> reproduce: (https://download.01.org/0day-ci/archive/20230621/202306210727.vqY7wkdG-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/202306210727.vqY7wkdG-lkp@intel.com/
> 
> Note: the linux-next/master HEAD 9dbf40840551df336c95ce2a3adbdd25ed53c0ef builds fine.
>       It may have been fixed somewhere.
> 
> All errors (new ones prefixed by >>):
> 
> >> kernel/rcu/rcuscale.c:301:27: error: 'get_rcu_tasks_gp_kthread' undeclared here (not in a function); did you mean 'get_rcu_tasks_trace_gp_kthread'?
>      301 |         .rso_gp_kthread = get_rcu_tasks_gp_kthread,
>          |                           ^~~~~~~~~~~~~~~~~~~~~~~~
>          |                           get_rcu_tasks_trace_gp_kthread

This should be fixed by Arnd's commit in -rcu:

d22c97e39866 ("rcuscale: fix building with RCU_TINY")

Please let me know if this one does not do the trick.

							Thanx, Paul

> vim +301 kernel/rcu/rcuscale.c
> 
>    289	
>    290	static struct rcu_scale_ops tasks_ops = {
>    291		.ptype		= RCU_TASKS_FLAVOR,
>    292		.init		= rcu_sync_scale_init,
>    293		.readlock	= tasks_scale_read_lock,
>    294		.readunlock	= tasks_scale_read_unlock,
>    295		.get_gp_seq	= rcu_no_completed,
>    296		.gp_diff	= rcu_seq_diff,
>    297		.async		= call_rcu_tasks,
>    298		.gp_barrier	= rcu_barrier_tasks,
>    299		.sync		= synchronize_rcu_tasks,
>    300		.exp_sync	= synchronize_rcu_tasks,
>  > 301		.rso_gp_kthread	= get_rcu_tasks_gp_kthread,
>    302		.name		= "tasks"
>    303	};
>    304	
> 
> -- 
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki


      reply	other threads:[~2023-06-20 23:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20 23:28 kernel test robot
2023-06-20 23:33 ` Paul E. McKenney [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=2d68cbf4-ef8e-44e9-a6f7-dbd27ca0ac70@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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