From: kernel test robot <lkp@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org, x86@kernel.org
Subject: [tip:tmp.tmp2 108/364] arch/x86/include/asm/uaccess.h:47:16: error: implicit declaration of function 'in_task'; did you mean 'rt_task'?
Date: Mon, 14 Jun 2021 05:38:21 +0800 [thread overview]
Message-ID: <202106140512.yK5B4DrZ-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3502 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tmp.tmp2
head: adcceb5eb7aee38e4a9c15bdf599655f0e1b1324
commit: a8bbfcd6b3ffac4ebcc0deb770d628fe6b8f2d05 [108/364] sched/headers: Remove <linux/mutex.h> from <linux/sched.h>
config: i386-defconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=a8bbfcd6b3ffac4ebcc0deb770d628fe6b8f2d05
git remote add tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
git fetch --no-tags tip tmp.tmp2
git checkout a8bbfcd6b3ffac4ebcc0deb770d628fe6b8f2d05
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from include/linux/export.h:43,
from include/linux/linkage.h:7,
from include/linux/kernel.h:10,
from kernel/locking/rwsem.c:19:
arch/x86/include/asm/uaccess.h: In function 'user_access_begin':
>> arch/x86/include/asm/uaccess.h:47:16: error: implicit declaration of function 'in_task'; did you mean 'rt_task'? [-Werror=implicit-function-declaration]
47 | WARN_ON_ONCE(!in_task() && !pagefault_disabled())
| ^~~~~~~
include/linux/compiler.h:78:42: note: in definition of macro 'unlikely'
78 | # define unlikely(x) __builtin_expect(!!(x), 0)
| ^
arch/x86/include/asm/uaccess.h:47:2: note: in expansion of macro 'WARN_ON_ONCE'
47 | WARN_ON_ONCE(!in_task() && !pagefault_disabled())
| ^~~~~~~~~~~~
arch/x86/include/asm/uaccess.h:71:2: note: in expansion of macro 'WARN_ON_IN_IRQ'
71 | WARN_ON_IN_IRQ(); \
| ^~~~~~~~~~~~~~
arch/x86/include/asm/uaccess.h:476:16: note: in expansion of macro 'access_ok'
476 | if (unlikely(!access_ok(ptr,len)))
| ^~~~~~~~~
cc1: some warnings being treated as errors
vim +47 arch/x86/include/asm/uaccess.h
ca23386216b9d4 include/asm-x86/uaccess.h Glauber Costa 2008-06-13 43
7c4788950ba592 arch/x86/include/asm/uaccess.h Peter Zijlstra 2016-11-22 44 #ifdef CONFIG_DEBUG_ATOMIC_SLEEP
2d8d8fac3b4eab arch/x86/include/asm/uaccess.h Masami Hiramatsu 2019-05-15 45 static inline bool pagefault_disabled(void);
2d8d8fac3b4eab arch/x86/include/asm/uaccess.h Masami Hiramatsu 2019-05-15 46 # define WARN_ON_IN_IRQ() \
2d8d8fac3b4eab arch/x86/include/asm/uaccess.h Masami Hiramatsu 2019-05-15 @47 WARN_ON_ONCE(!in_task() && !pagefault_disabled())
7c4788950ba592 arch/x86/include/asm/uaccess.h Peter Zijlstra 2016-11-22 48 #else
7c4788950ba592 arch/x86/include/asm/uaccess.h Peter Zijlstra 2016-11-22 49 # define WARN_ON_IN_IRQ()
7c4788950ba592 arch/x86/include/asm/uaccess.h Peter Zijlstra 2016-11-22 50 #endif
7c4788950ba592 arch/x86/include/asm/uaccess.h Peter Zijlstra 2016-11-22 51
:::::: The code at line 47 was first introduced by commit
:::::: 2d8d8fac3b4eab035dcd0068e1f5a746a697fbb3 x86/uaccess: Allow access_ok() in irq context if pagefault_disabled
:::::: TO: Masami Hiramatsu <mhiramat@kernel.org>
:::::: CC: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29247 bytes --]
reply other threads:[~2021-06-13 21:39 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=202106140512.yK5B4DrZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®