From: kbuild test robot <lkp@intel.com>
To: Clark Williams <williams@redhat.com>
Cc: kbuild-all@01.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH RT] rt: convert mm/kasan/quarantine_lock to raw_spinlock
Date: Wed, 19 Sep 2018 04:34:50 +0800 [thread overview]
Message-ID: <201809190442.itGUBZK3%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180918152931.17322-1-williams@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3095 bytes --]
Hi Clark,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linux-rt-devel/for-kbuild-bot/current-stable]
url: https://github.com/0day-ci/linux/commits/Clark-Williams/rt-convert-mm-kasan-quarantine_lock-to-raw_spinlock/20180919-021343
base: https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git for-kbuild-bot/current-stable
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
include/uapi/linux/perf_event.h:147:56: warning: cast truncates bits from constant value (8000000000000000 becomes 0)
kernel/rcu/tree.c:216:15: warning: symbol 'rcu_rnp_online_cpus' was not declared. Should it be static?
kernel/rcu/tree.c:366:6: warning: symbol 'rcu_dynticks_curr_cpu_in_eqs' was not declared. Should it be static?
>> kernel/rcu/tree.c:2930:36: warning: incorrect type in initializer (different address spaces)
kernel/rcu/tree.c:2930:36: expected struct task_struct [noderef] <asn:3>**store
kernel/rcu/tree.c:2930:36: got struct task_struct *[noderef] <asn:3>*<noident>
kernel/rcu/tree.c:3978:21: warning: incorrect type in argument 1 (different modifiers)
kernel/rcu/tree.c:3978:21: expected int ( *threadfn )( ... )
kernel/rcu/tree.c:3978:21: got int ( [noreturn] *<noident> )( ... )
kernel/rcu/tree.c:1680:13: warning: context imbalance in 'rcu_start_this_gp' - different lock contexts for basic block
kernel/rcu/tree.c:2703:9: warning: context imbalance in 'force_qs_rnp' - different lock contexts for basic block
kernel/rcu/tree.c:2766:25: warning: context imbalance in 'force_quiescent_state' - unexpected unlock
kernel/rcu/tree_exp.h:203:9: warning: context imbalance in '__rcu_report_exp_rnp' - different lock contexts for basic block
vim +2930 kernel/rcu/tree.c
385c3906 Paul E. McKenney 2013-11-04 2928
385c3906 Paul E. McKenney 2013-11-04 2929 static struct smp_hotplug_thread rcu_cpu_thread_spec = {
385c3906 Paul E. McKenney 2013-11-04 @2930 .store = &rcu_cpu_kthread_task,
385c3906 Paul E. McKenney 2013-11-04 2931 .thread_should_run = rcu_cpu_kthread_should_run,
385c3906 Paul E. McKenney 2013-11-04 2932 .thread_fn = rcu_cpu_kthread,
385c3906 Paul E. McKenney 2013-11-04 2933 .thread_comm = "rcuc/%u",
385c3906 Paul E. McKenney 2013-11-04 2934 .setup = rcu_cpu_kthread_setup,
385c3906 Paul E. McKenney 2013-11-04 2935 .park = rcu_cpu_kthread_park,
385c3906 Paul E. McKenney 2013-11-04 2936 };
385c3906 Paul E. McKenney 2013-11-04 2937
:::::: The code at line 2930 was first introduced by commit
:::::: 385c3906e2a7db036cd3185d1a2f38c842664ce0 rcu: Eliminate softirq processing from rcutree
:::::: TO: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
:::::: CC: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 64656 bytes --]
next prev parent reply other threads:[~2018-09-18 20:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 15:29 [PATCH RT] rt: convert mm/kasan/quarantine_lock to raw_spinlock Clark Williams
2018-09-18 20:34 ` kbuild test robot [this message]
2018-10-05 16:37 ` Sebastian Andrzej Siewior
2018-10-18 9:04 ` [kbuild-all] " Rong Chen
2018-10-05 16:30 ` [PATCH] kasan: convert kasan/quarantine_lock " Sebastian Andrzej Siewior
2018-10-05 16:33 ` Sebastian Andrzej Siewior
2018-10-08 0:47 ` Clark Williams
2018-10-08 9:15 ` Dmitry Vyukov
2018-10-09 14:27 ` Sebastian Andrzej Siewior
2018-10-10 8:25 ` Dmitry Vyukov
2018-10-10 9:29 ` Sebastian Andrzej Siewior
2018-10-10 9:45 ` Dmitry Vyukov
2018-10-10 9:53 ` Sebastian Andrzej Siewior
2018-10-10 9:57 ` Dmitry Vyukov
2018-10-10 21:49 ` [PATCH] mm/kasan: make quarantine_lock a raw_spinlock_t Sebastian Andrzej Siewior
2018-10-11 8:03 ` Dmitry Vyukov
2018-10-12 23:56 ` Andrew Morton
2018-10-13 13:50 ` Peter Zijlstra
2018-10-13 13:50 ` Peter Zijlstra
2018-10-15 23:35 ` Andrew Morton
2018-10-19 10:58 ` Peter Zijlstra
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=201809190442.itGUBZK3%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=bigeasy@linutronix.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.