The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<devel@driverdev.osuosl.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-perf-users@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [driver-core:pmu_bus] [perf/core]  8c8ac498a0: sysfs:cannot_create_duplicate_filename
Date: Wed, 19 Feb 2025 13:59:30 +0800	[thread overview]
Message-ID: <202502191352.b65c904c-lkp@intel.com> (raw)



Hello,

kernel test robot noticed "sysfs:cannot_create_duplicate_filename" on:

commit: 8c8ac498a0c5d8e68247800639bfb554bb65c782 ("perf/core: move all of the pmu devices into their own location")
https://git.kernel.org/cgit/linux/kernel/git/gregkh/driver-core.git pmu_bus

in testcase: boot

config: x86_64-randconfig-071-20250217
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G

(please refer to attached dmesg/kmsg for entire log/backtrace)


+--------------------------------------------------------+------------+------------+
|                                                        | 5c96041392 | 8c8ac498a0 |
+--------------------------------------------------------+------------+------------+
| sysfs:cannot_create_duplicate_filename                 | 0          | 6          |
| WARNING:at_kernel/events/core.c:#perf_event_sysfs_init | 0          | 6          |
| RIP:perf_event_sysfs_init                              | 0          | 6          |
+--------------------------------------------------------+------------+------------+


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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202502191352.b65c904c-lkp@intel.com


[    9.537939][    T1] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer
[    9.539489][    T1] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2c9477ac655, max_idle_ns: 440795235027 ns
[    9.555343][    T1] AVX2 or AES-NI instructions are not detected.
[    9.557309][    T1] AES CTR mode by8 optimization enabled
[    9.558531][    T1] sm3_avx_x86_64: BMI2 instruction are not detected.
[    9.574389][    T1] sysfs: cannot create duplicate filename '/devices/pmu_bus/power'
[    9.575589][    T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.14.0-rc1-00002-g8c8ac498a0c5 #1 95963aaeb84018cf4204d4190168e0e20d73ea75
[    9.575599][    T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[    9.575602][    T1] Call Trace:
[    9.575604][    T1]  <TASK>
[ 9.575608][ T1] dump_stack_lvl (kbuild/src/consumer/lib/dump_stack.c:123) 
[ 9.575629][ T1] sysfs_warn_dup (kbuild/src/consumer/fs/sysfs/dir.c:32) 
[ 9.575636][ T1] sysfs_create_dir_ns (kbuild/src/consumer/fs/sysfs/dir.c:63) 
[ 9.575641][ T1] ? __pfx_sysfs_create_dir_ns (kbuild/src/consumer/fs/sysfs/dir.c:41) 


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250219/202502191352.b65c904c-lkp@intel.com



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


                 reply	other threads:[~2025-02-19  5:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202502191352.b65c904c-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=oe-lkp@lists.linux.dev \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox