Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
* Re: [PATCH V8 2/6] perf: attach/detach PMU specific data
       [not found] <20250312182525.4078433-2-kan.liang@linux.intel.com>
@ 2025-03-12 23:23 ` kernel test robot
  2025-03-12 23:46 ` kernel test robot
  1 sibling, 0 replies; 4+ messages in thread
From: kernel test robot @ 2025-03-12 23:23 UTC (permalink / raw)
  To: kan.liang; +Cc: llvm, oe-kbuild-all

Hi,

kernel test robot noticed the following build errors:

[auto build test ERROR on tip/perf/core]
[also build test ERROR on next-20250312]
[cannot apply to perf-tools-next/perf-tools-next perf-tools/perf-tools linus/master acme/perf/core v6.14-rc6]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/kan-liang-linux-intel-com/perf-attach-detach-PMU-specific-data/20250313-022851
base:   tip/perf/core
patch link:    https://lore.kernel.org/r/20250312182525.4078433-2-kan.liang%40linux.intel.com
patch subject: [PATCH V8 2/6] perf: attach/detach PMU specific data
config: i386-buildonly-randconfig-005-20250313 (https://download.01.org/0day-ci/archive/20250313/202503130704.dGVT7UMi-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250313/202503130704.dGVT7UMi-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202503130704.dGVT7UMi-lkp@intel.com/

All errors (new ones prefixed by >>):

>> kernel/events/core.c:5604:13: error: no member named 'security' in 'struct perf_event'
    5604 |         if (event->security)
         |             ~~~~~  ^
   1 error generated.


vim +5604 kernel/events/core.c

  5600	
  5601	/* vs perf_event_alloc() error */
  5602	static void __free_event(struct perf_event *event)
  5603	{
> 5604		if (event->security)
  5605			security_perf_event_free(event);
  5606	
  5607		if (event->attach_state & PERF_ATTACH_CALLCHAIN)
  5608			put_callchain_buffers();
  5609	
  5610		kfree(event->addr_filter_ranges);
  5611	
  5612		if (event->attach_state & PERF_ATTACH_EXCLUSIVE)
  5613			exclusive_event_destroy(event);
  5614	
  5615		if (is_cgroup_event(event))
  5616			perf_detach_cgroup(event);
  5617	
  5618		if (event->destroy)
  5619			event->destroy(event);
  5620	
  5621		/*
  5622		 * Must be after ->destroy(), due to uprobe_perf_close() using
  5623		 * hw.target.
  5624		 */
  5625		if (event->hw.target)
  5626			put_task_struct(event->hw.target);
  5627	
  5628		if (event->pmu_ctx) {
  5629			/*
  5630			 * put_pmu_ctx() needs an event->ctx reference, because of
  5631			 * epc->ctx.
  5632			 */
  5633			WARN_ON_ONCE(!event->ctx);
  5634			WARN_ON_ONCE(event->pmu_ctx->ctx != event->ctx);
  5635			put_pmu_ctx(event->pmu_ctx);
  5636		}
  5637	
  5638		/*
  5639		 * perf_event_free_task() relies on put_ctx() being 'last', in
  5640		 * particular all task references must be cleaned up.
  5641		 */
  5642		if (event->ctx)
  5643			put_ctx(event->ctx);
  5644	
  5645		if (event->pmu)
  5646			module_put(event->pmu->module);
  5647	
  5648		call_rcu(&event->rcu_head, free_event_rcu);
  5649	}
  5650	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH V8 2/6] perf: attach/detach PMU specific data
       [not found] <20250312182525.4078433-2-kan.liang@linux.intel.com>
  2025-03-12 23:23 ` [PATCH V8 2/6] perf: attach/detach PMU specific data kernel test robot
@ 2025-03-12 23:46 ` kernel test robot
  2025-03-13 15:09   ` Nathan Chancellor
  1 sibling, 1 reply; 4+ messages in thread
From: kernel test robot @ 2025-03-12 23:46 UTC (permalink / raw)
  To: kan.liang; +Cc: llvm, oe-kbuild-all

Hi,

kernel test robot noticed the following build errors:

[auto build test ERROR on tip/perf/core]
[also build test ERROR on next-20250312]
[cannot apply to perf-tools-next/perf-tools-next perf-tools/perf-tools linus/master acme/perf/core v6.14-rc6]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/kan-liang-linux-intel-com/perf-attach-detach-PMU-specific-data/20250313-022851
base:   tip/perf/core
patch link:    https://lore.kernel.org/r/20250312182525.4078433-2-kan.liang%40linux.intel.com
patch subject: [PATCH V8 2/6] perf: attach/detach PMU specific data
config: csky-randconfig-002-20250313 (https://download.01.org/0day-ci/archive/20250313/202503130756.2j1ZuGT4-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250313/202503130756.2j1ZuGT4-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202503130756.2j1ZuGT4-lkp@intel.com/

All errors (new ones prefixed by >>):

   kernel/events/core.c: In function '__free_event':
>> kernel/events/core.c:5604:18: error: 'struct perf_event' has no member named 'security'
    5604 |         if (event->security)
         |                  ^~


vim +5604 kernel/events/core.c

  5600	
  5601	/* vs perf_event_alloc() error */
  5602	static void __free_event(struct perf_event *event)
  5603	{
> 5604		if (event->security)
  5605			security_perf_event_free(event);
  5606	
  5607		if (event->attach_state & PERF_ATTACH_CALLCHAIN)
  5608			put_callchain_buffers();
  5609	
  5610		kfree(event->addr_filter_ranges);
  5611	
  5612		if (event->attach_state & PERF_ATTACH_EXCLUSIVE)
  5613			exclusive_event_destroy(event);
  5614	
  5615		if (is_cgroup_event(event))
  5616			perf_detach_cgroup(event);
  5617	
  5618		if (event->destroy)
  5619			event->destroy(event);
  5620	
  5621		/*
  5622		 * Must be after ->destroy(), due to uprobe_perf_close() using
  5623		 * hw.target.
  5624		 */
  5625		if (event->hw.target)
  5626			put_task_struct(event->hw.target);
  5627	
  5628		if (event->pmu_ctx) {
  5629			/*
  5630			 * put_pmu_ctx() needs an event->ctx reference, because of
  5631			 * epc->ctx.
  5632			 */
  5633			WARN_ON_ONCE(!event->ctx);
  5634			WARN_ON_ONCE(event->pmu_ctx->ctx != event->ctx);
  5635			put_pmu_ctx(event->pmu_ctx);
  5636		}
  5637	
  5638		/*
  5639		 * perf_event_free_task() relies on put_ctx() being 'last', in
  5640		 * particular all task references must be cleaned up.
  5641		 */
  5642		if (event->ctx)
  5643			put_ctx(event->ctx);
  5644	
  5645		if (event->pmu)
  5646			module_put(event->pmu->module);
  5647	
  5648		call_rcu(&event->rcu_head, free_event_rcu);
  5649	}
  5650	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH V8 2/6] perf: attach/detach PMU specific data
  2025-03-12 23:46 ` kernel test robot
@ 2025-03-13 15:09   ` Nathan Chancellor
  2025-03-13 23:06     ` Philip Li
  0 siblings, 1 reply; 4+ messages in thread
From: Nathan Chancellor @ 2025-03-13 15:09 UTC (permalink / raw)
  To: kernel test robot; +Cc: llvm, oe-kbuild-all

Hi Intel folks,

On Thu, Mar 13, 2025 at 07:46:26AM +0800, kernel test robot wrote:
...
> url:    https://github.com/intel-lab-lkp/linux/commits/kan-liang-linux-intel-com/perf-attach-detach-PMU-specific-data/20250313-022851
> base:   tip/perf/core
> patch link:    https://lore.kernel.org/r/20250312182525.4078433-2-kan.liang%40linux.intel.com
> patch subject: [PATCH V8 2/6] perf: attach/detach PMU specific data
> config: csky-randconfig-002-20250313 (https://download.01.org/0day-ci/archive/20250313/202503130756.2j1ZuGT4-lkp@intel.com/config)
> compiler: csky-linux-gcc (GCC) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250313/202503130756.2j1ZuGT4-lkp@intel.com/reproduce)

I am noticing a number of recent reports that are being sent to our
mailing list (llvm@lists.linux.dev) when the compiler is not clang, is
something wrong with your filtering? Here are a number of examples:

https://lore.kernel.org/202503130708.AmtUDVfq-lkp@intel.com/
https://lore.kernel.org/202503131646.3EOj6ycs-lkp@intel.com/
https://lore.kernel.org/202503131715.Fb6CfjhT-lkp@intel.com/
https://lore.kernel.org/202503132205.Ajz52k8I-lkp@intel.com/
https://lore.kernel.org/202503132205.Vf8imlWS-lkp@intel.com/
https://lore.kernel.org/202503132256.f6p359iT-lkp@intel.com/

Cheers,
Nathan

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH V8 2/6] perf: attach/detach PMU specific data
  2025-03-13 15:09   ` Nathan Chancellor
@ 2025-03-13 23:06     ` Philip Li
  0 siblings, 0 replies; 4+ messages in thread
From: Philip Li @ 2025-03-13 23:06 UTC (permalink / raw)
  To: Nathan Chancellor; +Cc: kernel test robot, llvm, oe-kbuild-all

On Thu, Mar 13, 2025 at 04:09:02PM +0100, Nathan Chancellor wrote:
> Hi Intel folks,
> 
> On Thu, Mar 13, 2025 at 07:46:26AM +0800, kernel test robot wrote:
> ...
> > url:    https://github.com/intel-lab-lkp/linux/commits/kan-liang-linux-intel-com/perf-attach-detach-PMU-specific-data/20250313-022851
> > base:   tip/perf/core
> > patch link:    https://lore.kernel.org/r/20250312182525.4078433-2-kan.liang%40linux.intel.com
> > patch subject: [PATCH V8 2/6] perf: attach/detach PMU specific data
> > config: csky-randconfig-002-20250313 (https://download.01.org/0day-ci/archive/20250313/202503130756.2j1ZuGT4-lkp@intel.com/config)
> > compiler: csky-linux-gcc (GCC) 14.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250313/202503130756.2j1ZuGT4-lkp@intel.com/reproduce)
> 
> I am noticing a number of recent reports that are being sent to our
> mailing list (llvm@lists.linux.dev) when the compiler is not clang, is
> something wrong with your filtering? Here are a number of examples:

Sorry, there's a bug introduced in the bot but not noticed, I will fix it asap.

> 
> https://lore.kernel.org/202503130708.AmtUDVfq-lkp@intel.com/
> https://lore.kernel.org/202503131646.3EOj6ycs-lkp@intel.com/
> https://lore.kernel.org/202503131715.Fb6CfjhT-lkp@intel.com/
> https://lore.kernel.org/202503132205.Ajz52k8I-lkp@intel.com/
> https://lore.kernel.org/202503132205.Vf8imlWS-lkp@intel.com/
> https://lore.kernel.org/202503132256.f6p359iT-lkp@intel.com/
> 
> Cheers,
> Nathan
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2025-03-13 23:06 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20250312182525.4078433-2-kan.liang@linux.intel.com>
2025-03-12 23:23 ` [PATCH V8 2/6] perf: attach/detach PMU specific data kernel test robot
2025-03-12 23:46 ` kernel test robot
2025-03-13 15:09   ` Nathan Chancellor
2025-03-13 23:06     ` Philip Li

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox