From: kernel test robot <lkp@intel.com>
To: guoren@kernel.org, palmerdabbelt@google.com,
paul.walmsley@sifive.com, anup@brainfault.org,
greentime.hu@sifive.com, zong.li@sifive.com, me@packi.ch,
bjorn.topel@gmail.com, atish.patra@wdc.com
Cc: kbuild-all@lists.01.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V1 5/5] riscv: Add uprobes supported
Date: Tue, 7 Jul 2020 23:28:57 +0800 [thread overview]
Message-ID: <202007072325.YnrvwIpP%lkp@intel.com> (raw)
In-Reply-To: <1593833659-26224-6-git-send-email-guoren@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 3641 bytes --]
Hi,
I love your patch! Perhaps something to improve:
[auto build test WARNING on v5.8-rc2]
[cannot apply to linus/master v5.8-rc3 next-20200707]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/guoren-kernel-org/riscv-Add-k-uprobe-supported/20200704-113653
base: 48778464bb7d346b47157d21ffde2af6b2d39110
config: riscv-randconfig-s032-20200707 (attached as .config)
compiler: riscv32-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.2-31-gabbfd661-dirty
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
kernel/events/uprobes.c:1977:33: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
kernel/events/uprobes.c:1977:33: sparse: expected struct spinlock [usertype] *lock
kernel/events/uprobes.c:1977:33: sparse: got struct spinlock [noderef] __rcu *
kernel/events/uprobes.c:1979:35: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
kernel/events/uprobes.c:1979:35: sparse: expected struct spinlock [usertype] *lock
kernel/events/uprobes.c:1979:35: sparse: got struct spinlock [noderef] __rcu *
kernel/events/uprobes.c:2279:31: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
kernel/events/uprobes.c:2279:31: sparse: expected struct spinlock [usertype] *lock
kernel/events/uprobes.c:2279:31: sparse: got struct spinlock [noderef] __rcu *
kernel/events/uprobes.c:2281:33: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct spinlock [usertype] *lock @@ got struct spinlock [noderef] __rcu * @@
kernel/events/uprobes.c:2281:33: sparse: expected struct spinlock [usertype] *lock
kernel/events/uprobes.c:2281:33: sparse: got struct spinlock [noderef] __rcu *
>> include/asm-generic/mmiowb.h:56:9: sparse: sparse: context imbalance in '__replace_page' - unexpected unlock
vim +/__replace_page +56 include/asm-generic/mmiowb.h
d1be6a28b13ce6 Will Deacon 2019-02-22 46
d1be6a28b13ce6 Will Deacon 2019-02-22 47 static inline void mmiowb_spin_unlock(void)
d1be6a28b13ce6 Will Deacon 2019-02-22 48 {
d1be6a28b13ce6 Will Deacon 2019-02-22 49 struct mmiowb_state *ms = __mmiowb_state();
d1be6a28b13ce6 Will Deacon 2019-02-22 50
d1be6a28b13ce6 Will Deacon 2019-02-22 51 if (unlikely(ms->mmiowb_pending)) {
d1be6a28b13ce6 Will Deacon 2019-02-22 52 ms->mmiowb_pending = 0;
d1be6a28b13ce6 Will Deacon 2019-02-22 53 mmiowb();
d1be6a28b13ce6 Will Deacon 2019-02-22 54 }
d1be6a28b13ce6 Will Deacon 2019-02-22 55
d1be6a28b13ce6 Will Deacon 2019-02-22 @56 ms->nesting_count--;
---
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: 24543 bytes --]
next prev parent reply other threads:[~2020-07-07 15:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 3:34 [PATCH V1 0/5] riscv: Add k/uprobe supported guoren
2020-07-04 3:34 ` [PATCH V1 1/5] riscv: Fixup __vdso_gettimeofday broke dynamic ftrace guoren
2020-07-04 3:34 ` [PATCH V1 2/5] RISC-V: Implement ptrace regs and stack API guoren
2020-07-07 8:21 ` Zong Li
2020-07-04 3:34 ` [PATCH V1 3/5] riscv: Fixup compile error BUILD_BUG_ON failed guoren
2020-07-04 3:34 ` [PATCH V1 4/5] riscv: Add kprobes supported guoren
2020-07-06 10:11 ` Masami Hiramatsu
2020-07-07 8:25 ` Zong Li
2020-07-07 8:53 ` Guo Ren
2020-07-04 3:34 ` [PATCH V1 5/5] riscv: Add uprobes supported guoren
2020-07-07 15:28 ` kernel test robot [this message]
2020-07-04 6:39 ` [PATCH V1 0/5] riscv: Add k/uprobe supported Pekka Enberg
2020-07-04 14:55 ` Guo Ren
2020-07-04 18:30 ` Pekka Enberg
2020-07-14 18:43 ` Palmer Dabbelt
2020-07-15 5:01 ` Guo Ren
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=202007072325.YnrvwIpP%lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=bjorn.topel@gmail.com \
--cc=greentime.hu@sifive.com \
--cc=guoren@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=me@packi.ch \
--cc=palmerdabbelt@google.com \
--cc=paul.walmsley@sifive.com \
--cc=zong.li@sifive.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 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).