linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	jdike@addtoit.com, richard@nod.at,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [rcu:rcu/next 25/36] include/linux/irqflags.h:79:3: error: implicit declaration of function 'arch_irqs_disabled_flags'
Date: Tue, 14 Jun 2016 15:54:17 -0700	[thread overview]
Message-ID: <20160614225417.GR3923@linux.vnet.ibm.com> (raw)
In-Reply-To: <201606060200.kVmeQzvA%fengguang.wu@intel.com>

On Mon, Jun 06, 2016 at 02:04:03AM +0800, kbuild test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
> head:   13ee0de9cd2444b57ce30c4f1607b49b90aa0c38
> commit: f251ac814fc5787765009e60d54a2bd4277350c8 [25/36] rcu: Make call_rcu_tasks() tolerate first call with irqs disabled
> config: um-allmodconfig (attached as .config)
> compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
> reproduce:
>         git checkout f251ac814fc5787765009e60d54a2bd4277350c8
>         # save the attached .config to linux build tree
>         make ARCH=um 

My kneejerk reaction would be to make CONFIG_TASKS_RCU depend on
!UML or something similar.

Another approach would be create a arch_irqs_disabled_flags() for UML.

Any preferences?

							Thanx, Paul

> All errors (new ones prefixed by >>):
> 
>    In file included from include/linux/spinlock.h:53:0,
>                     from kernel/rcu/update.c:36:
>    kernel/rcu/update.c: In function 'call_rcu_tasks':
> >> include/linux/irqflags.h:79:3: error: implicit declaration of function 'arch_irqs_disabled_flags' [-Werror=implicit-function-declaration]
>       arch_irqs_disabled_flags(flags); \
>       ^
>    include/linux/irqflags.h:149:36: note: in expansion of macro 'raw_irqs_disabled_flags'
>     #define irqs_disabled_flags(flags) raw_irqs_disabled_flags(flags)
>                                        ^~~~~~~~~~~~~~~~~~~~~~~
>    kernel/rcu/update.c:572:21: note: in expansion of macro 'irqs_disabled_flags'
>          (!havetask && !irqs_disabled_flags(flags))) {
>                         ^~~~~~~~~~~~~~~~~~~
>    cc1: some warnings being treated as errors
> 
> vim +/arch_irqs_disabled_flags +79 include/linux/irqflags.h
> 
> df9ee292 David Howells 2010-10-07  73  		typecheck(unsigned long, flags);	\
> df9ee292 David Howells 2010-10-07  74  		flags = arch_local_save_flags();	\
> df9ee292 David Howells 2010-10-07  75  	} while (0)
> df9ee292 David Howells 2010-10-07  76  #define raw_irqs_disabled_flags(flags)			\
> df9ee292 David Howells 2010-10-07  77  	({						\
> df9ee292 David Howells 2010-10-07  78  		typecheck(unsigned long, flags);	\
> df9ee292 David Howells 2010-10-07 @79  		arch_irqs_disabled_flags(flags);	\
> df9ee292 David Howells 2010-10-07  80  	})
> df9ee292 David Howells 2010-10-07  81  #define raw_irqs_disabled()		(arch_irqs_disabled())
> df9ee292 David Howells 2010-10-07  82  #define raw_safe_halt()			arch_safe_halt()
> 
> :::::: The code at line 79 was first introduced by commit
> :::::: df9ee29270c11dba7d0fe0b83ce47a4d8e8d2101 Fix IRQ flag handling naming
> 
> :::::: TO: David Howells <dhowells@redhat.com>
> :::::: CC: David Howells <dhowells@redhat.com>
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

  reply	other threads:[~2016-06-14 22:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-05 18:04 [rcu:rcu/next 25/36] include/linux/irqflags.h:79:3: error: implicit declaration of function 'arch_irqs_disabled_flags' kbuild test robot
2016-06-14 22:54 ` Paul E. McKenney [this message]
2016-06-15  7:05   ` Richard Weinberger
2016-06-15 12:45     ` Paul E. McKenney
2016-08-08 20:12       ` Richard Weinberger
2016-08-08 20:35         ` Paul E. McKenney
2016-12-14 21:54           ` Richard Weinberger
2016-12-15  0:16             ` 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=20160614225417.GR3923@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=fengguang.wu@intel.com \
    --cc=jdike@addtoit.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).