| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <202205130127.Ew9k8Q7Q-lkp@intel.com>
Date: Fri, 13 May 2022 01:59:49 +0800
From: kernel test robot <lkp@...el.com>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: kbuild-all@...ts.01.org, linux-kernel@...r.kernel.org
Subject: [frederic-dynticks:rcu/context-tracking-v2 17/21]
kernel/context_tracking.c:91:25: error: implicit declaration of function
'rcu_irq_work_resched'
tree: https://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git rcu/context-tracking-v2
head: 0364ddb8830db4d4b78f7bfd9344e12d22e9cd32
commit: 0fe61091f9b097b9f0ccc4ffe3333d7e80093392 [17/21] rcu/context-tracking: Move deferred nocb resched to context tracking
config: arm-randconfig-r006-20220512 (https://download.01.org/0day-ci/archive/20220513/202205130127.Ew9k8Q7Q-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.3.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://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git/commit/?id=0fe61091f9b097b9f0ccc4ffe3333d7e80093392
git remote add frederic-dynticks https://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
git fetch --no-tags frederic-dynticks rcu/context-tracking-v2
git checkout 0fe61091f9b097b9f0ccc4ffe3333d7e80093392
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@...el.com>
All errors (new ones prefixed by >>):
In file included from include/linux/vtime.h:5,
from include/linux/context_tracking.h:6,
from kernel/context_tracking.c:18:
include/linux/context_tracking_state.h: In function 'ct_dynticks_cpu_acquire':
include/linux/context_tracking_state.h:51:36: error: passing argument 1 of 'atomic_read_acquire' from incompatible pointer type [-Werror=incompatible-pointer-types]
51 | return atomic_read_acquire(&ct->state);
| ^~~~~~~~~~
| |
| enum ctx_state *
In file included from include/linux/atomic.h:82,
from include/linux/rcupdate.h:25,
from include/linux/rculist.h:11,
from include/linux/pid.h:5,
from include/linux/sched.h:14,
from include/linux/context_tracking.h:5,
from kernel/context_tracking.c:18:
include/linux/atomic/atomic-instrumented.h:32:37: note: expected 'const atomic_t *' but argument is of type 'enum ctx_state *'
32 | atomic_read_acquire(const atomic_t *v)
| ~~~~~~~~~~~~~~~~^
kernel/context_tracking.c: In function '__ct_user_enter':
>> kernel/context_tracking.c:91:25: error: implicit declaration of function 'rcu_irq_work_resched' [-Werror=implicit-function-declaration]
91 | rcu_irq_work_resched();
| ^~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/rcu_irq_work_resched +91 kernel/context_tracking.c
51
52 /**
53 * __ct_user_enter - Inform the context tracking that the CPU is going
54 * to enter user or guest space mode.
55 *
56 * This function must be called right before we switch from the kernel
57 * to user or guest space, when it's guaranteed the remaining kernel
58 * instructions to execute won't use any RCU read side critical section
59 * because this function sets RCU in extended quiescent state.
60 */
61 void noinstr __ct_user_enter(enum ctx_state state)
62 {
63 lockdep_assert_irqs_disabled();
64
65 /* Kernel threads aren't supposed to go to userspace */
66 WARN_ON_ONCE(!current->mm);
67
68 if (!context_tracking_recursion_enter())
69 return;
70
71 if ( __this_cpu_read(context_tracking.state) != state) {
72 if (__this_cpu_read(context_tracking.active)) {
73 /*
74 * At this stage, only low level arch entry code remains and
75 * then we'll run in userspace. We can assume there won't be
76 * any RCU read-side critical section until the next call to
77 * user_exit() or ct_irq_enter(). Let's remove RCU's dependency
78 * on the tick.
79 */
80 if (state == CONTEXT_USER) {
81 instrumentation_begin();
82 trace_user_enter(0);
83 vtime_user_enter(current);
84 instrumentation_end();
85 }
86 /*
87 * Other than generic entry implementation, we may be past the last
88 * rescheduling opportunity in the entry code. Trigger a self IPI
89 * that will fire and reschedule once we resume in user/guest mode.
90 */
> 91 rcu_irq_work_resched();
92 rcu_user_enter();
93 }
94 /*
95 * Even if context tracking is disabled on this CPU, because it's outside
96 * the full dynticks mask for example, we still have to keep track of the
97 * context transitions and states to prevent inconsistency on those of
98 * other CPUs.
99 * If a task triggers an exception in userspace, sleep on the exception
100 * handler and then migrate to another CPU, that new CPU must know where
101 * the exception returns by the time we call exception_exit().
102 * This information can only be provided by the previous CPU when it called
103 * exception_enter().
104 * OTOH we can spare the calls to vtime and RCU when context_tracking.active
105 * is false because we know that CPU is not tickless.
106 */
107 __this_cpu_write(context_tracking.state, state);
108 }
109 context_tracking_recursion_exit();
110 }
111 EXPORT_SYMBOL_GPL(__ct_user_enter);
112
--
0-DAY CI Kernel Test Service
https://01.org/lkp
Powered by blists - more mailing lists