public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: paulmck@kernel.org, kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
	linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: kernel/rcu/tree.c:2073:23: warning: stack frame size of 2704 bytes in function 'rcu_gp_kthread'
Date: Mon, 7 Jun 2021 17:18:21 +0800	[thread overview]
Message-ID: <4696fe3d-a7ad-acae-686e-6295ca327737@intel.com> (raw)
In-Reply-To: <20210606044926.GJ4397@paulmck-ThinkPad-P17-Gen-1>



On 6/6/21 12:49 PM, Paul E. McKenney wrote:
> On Sun, Jun 06, 2021 at 12:19:57PM +0800, kernel test robot wrote:
>> Hi Paul,
>>
>> FYI, the error/warning still remains.
>>
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head:   f5b6eb1e018203913dfefcf6fa988649ad11ad6e
>> commit: 7dffe01765d9309b8bd5505503933ec0ec53d192 rcu: Add lockdep_assert_irqs_disabled() to raw_spin_unlock_rcu_node() macros
>> date:   5 months ago
>> config: powerpc-randconfig-r023-20210606 (attached as .config)
>> compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 551a697c5cf33275b66add4fc467fcf59084cffb)
>> 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
>>          # install powerpc cross compiling tool for clang build
>>          # apt-get install binutils-powerpc-linux-gnu
>>          # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7dffe01765d9309b8bd5505503933ec0ec53d192
>>          git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>          git fetch --no-tags linus master
>>          git checkout 7dffe01765d9309b8bd5505503933ec0ec53d192
>>          # save the attached .config to linux build tree
>>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=powerpc
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All warnings (new ones prefixed by >>):
>>
>>     In file included from kernel/rcu/tree.c:21:
>>     In file included from include/linux/kernel.h:12:
>>     In file included from include/linux/bitops.h:29:
>>     In file included from arch/powerpc/include/asm/bitops.h:62:
>>     arch/powerpc/include/asm/barrier.h:49:9: warning: '__lwsync' macro redefined [-Wmacro-redefined]
>>     #define __lwsync()      __asm__ __volatile__ (stringify_in_c(LWSYNC) : : :"memory")
>>             ^
>>     <built-in>:310:9: note: previous definition is here
>>     #define __lwsync __builtin_ppc_lwsync
>>             ^
>>>> kernel/rcu/tree.c:2073:23: warning: stack frame size of 2704 bytes in function 'rcu_gp_kthread' [-Wframe-larger-than=]
>>     static int __noreturn rcu_gp_kthread(void *unused)
> Does -rcu commit 2f20de99a63b ("rcu: Make rcu_gp_cleanup() be noinline
> for tracing") help?

Hi Paul,

The stack frame size decreased to 2256 bytes:

   kernel/rcu/tree.c:2129:23: warning: stack frame size of 2256 bytes in 
function 'rcu_gp_kthread' [-Wframe-larger-than=]

Best Regards,
Rong Chen

  reply	other threads:[~2021-06-07  9:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-06  4:19 kernel/rcu/tree.c:2073:23: warning: stack frame size of 2704 bytes in function 'rcu_gp_kthread' kernel test robot
2021-06-06  4:49 ` Paul E. McKenney
2021-06-07  9:18   ` Rong Chen [this message]
2021-06-07 15:19     ` [kbuild-all] " Paul E. McKenney
2021-06-08  3:14       ` Rong Chen
2021-06-08  5:01         ` Paul E. McKenney
2021-06-08  5:34           ` Rong Chen
2021-06-08 15:53           ` Nathan Chancellor
2021-06-09  3:58             ` Paul E. McKenney
2021-06-09  4:14               ` Nathan Chancellor
2021-06-09 17:23                 ` Paul E. McKenney

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=4696fe3d-a7ad-acae-686e-6295ca327737@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --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