public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: kbuild-all@lists.01.org, Ammar Faizi <ammarfaizi2@gnuweeb.org>,
	GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
	linux-kernel@vger.kernel.org
Subject: [ammarfaizi2-block:paulmck/linux-rcu/dev.2022.09.03a 36/36] kernel/rcu/srcutree.c:647:1: error: 'u' undeclared; did you mean 'u8'?
Date: Wed, 21 Sep 2022 11:49:33 +0800	[thread overview]
Message-ID: <202209211114.7li0O31k-lkp@intel.com> (raw)

tree:   https://github.com/ammarfaizi2/linux-block paulmck/linux-rcu/dev.2022.09.03a
head:   607762184099b5d0b6765f69673fafa1d7eb4d30
commit: 607762184099b5d0b6765f69673fafa1d7eb4d30 [36/36] srcu: Check for consistent per-CPU per-srcu_struct NMI safety
config: parisc-randconfig-r005-20220921 (https://download.01.org/0day-ci/archive/20220921/202209211114.7li0O31k-lkp@intel.com/config)
compiler: hppa64-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/ammarfaizi2/linux-block/commit/607762184099b5d0b6765f69673fafa1d7eb4d30
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block paulmck/linux-rcu/dev.2022.09.03a
        git checkout 607762184099b5d0b6765f69673fafa1d7eb4d30
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=parisc64 SHELL=/bin/bash kernel/rcu/

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   kernel/rcu/srcutree.c: In function 'srcu_check_nmi_safety':
>> kernel/rcu/srcutree.c:647:1: error: 'u' undeclared (first use in this function); did you mean 'u8'?
     647 | u);
         | ^
         | u8
   kernel/rcu/srcutree.c:647:1: note: each undeclared identifier is reported only once for each function it appears in
>> kernel/rcu/srcutree.c:647:2: error: expected ';' before ')' token
     647 | u);
         |  ^
         |  ;
>> kernel/rcu/srcutree.c:647:2: error: expected statement before ')' token


vim +647 kernel/rcu/srcutree.c

   628	
   629	/*
   630	 * Check for consistent NMI safety.
   631	 */
   632	static void srcu_check_nmi_safety(struct srcu_struct *ssp, bool nmi_safe)
   633	{
   634		int nmi_safe_mask = 1 << nmi_safe;
   635		int old_nmi_safe_mask;
   636		struct srcu_data *sdp;
   637	
   638		if (!IS_ENABLED(CONFIG_PROVE_RCU))
   639			return;
   640		sdp = raw_cpu_ptr(ssp->sda);
   641		old_nmi_safe_mask = READ_ONCE(sdp->srcu_nmi_safety);
   642		if (!old_nmi_safe_mask) {
   643			WRITE_ONCE(sdp->srcu_nmi_safety, nmi_safe_mask);
   644			return;
   645		}
   646		WARN_ONCE(old_nmi_safe_mask != nmi_safe_mask, "CPU %d old state %d new state %d\n", sdp->cpu, old_nmi_safe_mask, nmi_safe_mask);
 > 647	u);
   648	}
   649	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-09-21  3:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202209211114.7li0O31k-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=gwml@vger.gnuweeb.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@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