All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC v2] perf: Rewrite core context handling
Date: Fri, 14 Jan 2022 03:15:38 +0800	[thread overview]
Message-ID: <202201140347.ue2Ckk9k-lkp@intel.com> (raw)
In-Reply-To: <20220113134743.1292-1-ravi.bangoria@amd.com>

[-- Attachment #1: Type: text/plain, Size: 13155 bytes --]

Hi Ravi,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on tip/perf/core]
[also build test WARNING on powerpc/next tip/sched/core v5.16 next-20220113]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Ravi-Bangoria/perf-Rewrite-core-context-handling/20220113-215022
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git a9f4a6e92b3b319296fb078da2615f618f6cd80c
config: i386-randconfig-s001 (https://download.01.org/0day-ci/archive/20220114/202201140347.ue2Ckk9k-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://github.com/0day-ci/linux/commit/f7cf7134e405062bf0f22c3ba5637241c4c4d06a
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Ravi-Bangoria/perf-Rewrite-core-context-handling/20220113-215022
        git checkout f7cf7134e405062bf0f22c3ba5637241c4c4d06a
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash kernel/events/

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/core.c:1440:15: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:1440:15: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:1440:15: sparse:    struct perf_event_context *
   kernel/events/core.c:1453:28: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:1453:28: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:1453:28: sparse:    struct perf_event_context *
   kernel/events/core.c:3478:20: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:3478:20: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:3478:20: sparse:    struct perf_event_context *
   kernel/events/core.c:3482:18: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:3482:18: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:3482:18: sparse:    struct perf_event_context *
   kernel/events/core.c:3483:23: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:3483:23: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:3483:23: sparse:    struct perf_event_context *
   kernel/events/core.c:3520:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:3520:25: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:3520:25: sparse:    struct perf_event_context *
   kernel/events/core.c:3521:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:3521:25: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:3521:25: sparse:    struct perf_event_context *
   kernel/events/core.c:3930:15: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:3930:15: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:3930:15: sparse:    struct perf_event_context *
   kernel/events/core.c:4334:15: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:4334:15: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:4334:15: sparse:    struct perf_event_context *
   kernel/events/core.c:4807:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:4807:25: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:4807:25: sparse:    struct perf_event_context *
>> kernel/events/core.c:4826:31: sparse: sparse: symbol 'find_get_pmu_context' was not declared. Should it be static?
   kernel/events/core.c:6188:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:6188:9: sparse:    struct perf_buffer [noderef] __rcu *
   kernel/events/core.c:6188:9: sparse:    struct perf_buffer *
   kernel/events/core.c:5650:24: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted __poll_t [usertype] events @@     got int @@
   kernel/events/core.c:5894:22: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:5894:22: sparse:    struct perf_buffer [noderef] __rcu *
   kernel/events/core.c:5894:22: sparse:    struct perf_buffer *
   kernel/events/core.c:6030:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:6030:14: sparse:    struct perf_buffer [noderef] __rcu *
   kernel/events/core.c:6030:14: sparse:    struct perf_buffer *
   kernel/events/core.c:6063:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:6063:14: sparse:    struct perf_buffer [noderef] __rcu *
   kernel/events/core.c:6063:14: sparse:    struct perf_buffer *
   kernel/events/core.c:6120:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:6120:14: sparse:    struct perf_buffer [noderef] __rcu *
   kernel/events/core.c:6120:14: sparse:    struct perf_buffer *
   kernel/events/core.c:6206:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:6206:14: sparse:    struct perf_buffer [noderef] __rcu *
   kernel/events/core.c:6206:14: sparse:    struct perf_buffer *
   kernel/events/core.c:6219:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:6219:14: sparse:    struct perf_buffer [noderef] __rcu *
   kernel/events/core.c:6219:14: sparse:    struct perf_buffer *
   kernel/events/core.c:7864:15: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:7864:15: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:7864:15: sparse:    struct perf_event_context *
   kernel/events/core.c:7910:15: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:7910:15: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:7910:15: sparse:    struct perf_event_context *
   kernel/events/core.c:7949:13: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:7949:13: sparse:    struct perf_buffer [noderef] __rcu *
   kernel/events/core.c:7949:13: sparse:    struct perf_buffer *
   kernel/events/core.c:8053:61: sparse: sparse: incorrect type in argument 2 (different address spaces) @@     expected struct task_struct *p @@     got struct task_struct [noderef] __rcu *real_parent @@
   kernel/events/core.c:8053:61: sparse:     expected struct task_struct *p
   kernel/events/core.c:8053:61: sparse:     got struct task_struct [noderef] __rcu *real_parent
   kernel/events/core.c:8055:61: sparse: sparse: incorrect type in argument 2 (different address spaces) @@     expected struct task_struct *p @@     got struct task_struct [noderef] __rcu *real_parent @@
   kernel/events/core.c:8055:61: sparse:     expected struct task_struct *p
   kernel/events/core.c:8055:61: sparse:     got struct task_struct [noderef] __rcu *real_parent
   kernel/events/core.c:8754:15: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:8754:15: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:8754:15: sparse:    struct perf_event_context *
   kernel/events/core.c:9745:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:9745:9: sparse:    struct swevent_hlist [noderef] __rcu *
   kernel/events/core.c:9745:9: sparse:    struct swevent_hlist *
   kernel/events/core.c:9784:17: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:9784:17: sparse:    struct swevent_hlist [noderef] __rcu *
   kernel/events/core.c:9784:17: sparse:    struct swevent_hlist *
   kernel/events/core.c:9965:23: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:9965:23: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:9965:23: sparse:    struct perf_event_context *
   kernel/events/core.c:11116:1: sparse: sparse: symbol 'dev_attr_nr_addr_filters' was not declared. Should it be static?
   kernel/events/core.c:12826:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:12826:9: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:12826:9: sparse:    struct perf_event_context *
   kernel/events/core.c:12920:15: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:12920:15: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:12920:15: sparse:    struct perf_event_context *
   kernel/events/core.c:12932:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:12932:9: sparse:    struct perf_event_context [noderef] __rcu *
   kernel/events/core.c:12932:9: sparse:    struct perf_event_context *
   kernel/events/core.c:13356:17: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:13356:17: sparse:    struct swevent_hlist [noderef] __rcu *
   kernel/events/core.c:13356:17: sparse:    struct swevent_hlist *
   kernel/events/core.c:161:9: sparse: sparse: context imbalance in 'perf_ctx_lock' - wrong count at exit
   kernel/events/core.c:169:17: sparse: sparse: context imbalance in 'perf_ctx_unlock' - unexpected unlock
   kernel/events/core.c: note: in included file (through include/linux/rcupdate.h, include/linux/rculist.h, include/linux/dcache.h, ...):
   include/linux/rcutiny.h:102:44: sparse: sparse: context imbalance in 'perf_lock_task_context' - different lock contexts for basic block
   kernel/events/core.c:1487:17: sparse: sparse: context imbalance in 'perf_pin_task_context' - unexpected unlock
   kernel/events/core.c:2815:9: sparse: sparse: context imbalance in '__perf_install_in_context' - wrong count at exit
   kernel/events/core.c:4781:17: sparse: sparse: context imbalance in 'find_get_context' - unexpected unlock
   kernel/events/core.c: note: in included file:
   kernel/events/internal.h:204:1: sparse: sparse: incorrect type in argument 2 (different address spaces) @@     expected void const [noderef] __user *from @@     got void const *buf @@
   kernel/events/core.c:9594:17: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:9594:17: sparse:    struct swevent_hlist [noderef] __rcu *
   kernel/events/core.c:9594:17: sparse:    struct swevent_hlist *
   kernel/events/core.c:9614:17: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:9614:17: sparse:    struct swevent_hlist [noderef] __rcu *
   kernel/events/core.c:9614:17: sparse:    struct swevent_hlist *
   kernel/events/core.c:9734:16: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:9734:16: sparse:    struct swevent_hlist [noderef] __rcu *
   kernel/events/core.c:9734:16: sparse:    struct swevent_hlist *
   kernel/events/core.c:9734:16: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:9734:16: sparse:    struct swevent_hlist [noderef] __rcu *
   kernel/events/core.c:9734:16: sparse:    struct swevent_hlist *
   kernel/events/core.c:9734:16: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/core.c:9734:16: sparse:    struct swevent_hlist [noderef] __rcu *
   kernel/events/core.c:9734:16: sparse:    struct swevent_hlist *

Please review and possibly fold the followup patch.

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  parent reply	other threads:[~2022-01-13 19:15 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 13:47 [RFC v2] perf: Rewrite core context handling Ravi Bangoria
2022-01-13 19:06 ` [RFC PATCH] perf: find_get_pmu_context can be static kernel test robot
2022-01-13 19:15 ` kernel test robot [this message]
2022-01-17  7:18 ` [perf] f7cf7134e4: WARNING:at_kernel/events/core.c:#__pmu_ctx_sched_out kernel test robot
2022-01-17  7:18   ` kernel test robot
2022-01-31  4:43 ` [RFC v2] perf: Rewrite core context handling Ravi Bangoria
2022-06-13 14:35 ` Peter Zijlstra
2022-06-13 14:36   ` Peter Zijlstra
2022-06-13 14:38   ` Peter Zijlstra
2022-08-02  6:11     ` Ravi Bangoria
2022-08-22 15:29       ` Peter Zijlstra
2022-08-22 15:43         ` Peter Zijlstra
2022-08-22 16:37           ` Ravi Bangoria
2022-08-23  4:20             ` Ravi Bangoria
2022-08-29  3:54               ` Ravi Bangoria
2022-08-23  6:30             ` Peter Zijlstra
2022-08-29  4:00             ` Ravi Bangoria
2022-08-29 11:58               ` Peter Zijlstra
2022-08-22 16:52       ` Peter Zijlstra
2022-08-23  4:57         ` Ravi Bangoria
2022-06-13 14:41   ` Peter Zijlstra
2022-08-22 14:38     ` Ravi Bangoria
2022-06-13 14:43   ` Peter Zijlstra
2022-08-02  6:16     ` Ravi Bangoria
2022-08-23  8:57       ` Peter Zijlstra
2022-08-24  5:07         ` Ravi Bangoria
2022-08-24  7:27           ` Peter Zijlstra
2022-08-24  7:53             ` Ravi Bangoria
2022-06-13 14:55   ` Peter Zijlstra
2022-08-02  6:10     ` Ravi Bangoria
2022-08-22 16:44       ` Peter Zijlstra
2022-08-23  4:46         ` Ravi Bangoria
2022-06-17 13:36   ` Peter Zijlstra
2022-08-24 10:13     ` Peter Zijlstra
2022-06-27  4:18   ` Ravi Bangoria
2022-08-02  6:06     ` Ravi Bangoria
2022-08-24 12:15   ` Peter Zijlstra
2022-08-24 14:59     ` Peter Zijlstra
2022-08-25  5:39       ` Ravi Bangoria
2022-08-25  9:17         ` Peter Zijlstra
2022-08-25 11:03       ` Ravi Bangoria
2022-08-02  6:13 ` Ravi Bangoria
2022-08-23  7:10   ` Peter Zijlstra
2022-08-02  6:17 ` Ravi Bangoria
2022-08-23  7:26   ` Peter Zijlstra
2022-08-23 15:14     ` Ravi Bangoria
2022-08-22 14:40 ` Ravi Bangoria
2022-01-14 21:48 kernel test robot
2022-01-18  6:01 ` kernel test robot
2022-01-18  6:01   ` kernel test robot

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=202201140347.ue2Ckk9k-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.