From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C87BAC5AE5E for ; Sat, 18 Nov 2023 08:51:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231902AbjKRI35 (ORCPT ); Sat, 18 Nov 2023 03:29:57 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52878 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229449AbjKRI3z (ORCPT ); Sat, 18 Nov 2023 03:29:55 -0500 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 45D45D6A for ; Sat, 18 Nov 2023 00:29:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1700296192; x=1731832192; h=date:from:to:cc:subject:message-id:mime-version; bh=+8GS8oJdfTBwH9Njn5eu4cnUAyw4QtmzgdfRsBeHqe0=; b=iadnc1NJmpQiwAienZI+eU3DJy6mKJ2Fd8Fco/h9AmuW7zQqVu13s7zN u2jiT8ECeywPUYbLng1ElGp0YThEKwUid2/Psdm/95YdOpoeHxE+6vuvr 6wO2ddpsh9VRdQ0T6Yuz7dQj2HeXteiQ3Lj4aOEIWRVMWg8zVhg1PJOT5 jm0baR97Vlwq3wrn0u/TBCv4tK/csI4ztxtvpb7L4PEU3ZLHDOQ/CAUPz +sUZgf4h9mFOqadipwywbkaFVSzsK7ihcRxahfuuZ2iCH/lyxCxvdECEy KlZmSngItuHz+IUwUXsinn6bq46kRBbvwIdOQeJQx5lidqNq3IYKr18ex w==; X-IronPort-AV: E=McAfee;i="6600,9927,10897"; a="371593093" X-IronPort-AV: E=Sophos;i="6.04,207,1695711600"; d="scan'208";a="371593093" Received: from fmviesa001.fm.intel.com ([10.60.135.141]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Nov 2023 00:29:51 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.04,207,1695711600"; d="scan'208";a="14124640" Received: from lkp-server02.sh.intel.com (HELO b8de5498638e) ([10.239.97.151]) by fmviesa001.fm.intel.com with ESMTP; 18 Nov 2023 00:29:50 -0800 Received: from kbuild by b8de5498638e with local (Exim 4.96) (envelope-from ) id 1r4Ghf-0003h9-0M; Sat, 18 Nov 2023 08:29:41 +0000 Date: Sat, 18 Nov 2023 16:29:06 +0800 From: kernel test robot To: "Paul E. McKenney" Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org, Frederic Weisbecker Subject: kernel/locking/locktorture.c:127:23: sparse: sparse: symbol 'call_rcu_chain' was not declared. Should it be static? Message-ID: <202311181621.k1LVEHqR-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 791c8ab095f71327899023223940dd52257a4173 commit: 7f993623e9ebcd633c0f760991e5078b95a37db3 locktorture: Add call_rcu_chains module parameter date: 8 weeks ago config: x86_64-randconfig-x001-20230717 (https://download.01.org/0day-ci/archive/20231118/202311181621.k1LVEHqR-lkp@intel.com/config) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231118/202311181621.k1LVEHqR-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 | Closes: https://lore.kernel.org/oe-kbuild-all/202311181621.k1LVEHqR-lkp@intel.com/ sparse warnings: (new ones prefixed by >>) >> kernel/locking/locktorture.c:127:23: sparse: sparse: symbol 'call_rcu_chain' was not declared. Should it be static? kernel/locking/locktorture.c:496:12: sparse: sparse: context imbalance in 'torture_mutex_lock' - wrong count at exit kernel/locking/locktorture.c:512:13: sparse: sparse: context imbalance in 'torture_mutex_unlock' - wrong count at exit kernel/locking/locktorture.c:570:12: sparse: sparse: context imbalance in 'torture_ww_mutex_lock' - wrong count at exit kernel/locking/locktorture.c: note: in included file: include/linux/ww_mutex.h:191:9: sparse: sparse: context imbalance in 'torture_ww_mutex_unlock' - wrong count at exit kernel/locking/locktorture.c:665:12: sparse: sparse: context imbalance in 'torture_rtmutex_lock' - wrong count at exit kernel/locking/locktorture.c:689:13: sparse: sparse: context imbalance in 'torture_rtmutex_unlock' - wrong count at exit kernel/locking/locktorture.c:729:12: sparse: sparse: context imbalance in 'torture_rwsem_down_write' - wrong count at exit kernel/locking/locktorture.c:745:13: sparse: sparse: context imbalance in 'torture_rwsem_up_write' - wrong count at exit kernel/locking/locktorture.c:751:12: sparse: sparse: context imbalance in 'torture_rwsem_down_read' - wrong count at exit kernel/locking/locktorture.c:769:13: sparse: sparse: context imbalance in 'torture_rwsem_up_read' - wrong count at exit kernel/locking/locktorture.c:799:12: sparse: sparse: context imbalance in 'torture_percpu_rwsem_down_write' - wrong count at exit kernel/locking/locktorture.c:806:13: sparse: sparse: context imbalance in 'torture_percpu_rwsem_up_write' - wrong count at exit kernel/locking/locktorture.c: note: in included file: include/linux/percpu-rwsem.h:70:9: sparse: sparse: context imbalance in 'torture_percpu_rwsem_down_read' - wrong count at exit include/linux/percpu-rwsem.h:121:9: sparse: sparse: context imbalance in 'torture_percpu_rwsem_up_read' - wrong count at exit vim +/call_rcu_chain +127 kernel/locking/locktorture.c 122 123 struct call_rcu_chain { 124 struct rcu_head crc_rh; 125 bool crc_stop; 126 }; > 127 struct call_rcu_chain *call_rcu_chain; 128 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki