From: kernel test robot <oliver.sang@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
<linux-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [workqueue] b188c57af2: sysfs:cannot_create_duplicate_filename
Date: Fri, 16 Aug 2024 12:08:17 +0800 [thread overview]
Message-ID: <202408161132.7c52d91a-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "sysfs:cannot_create_duplicate_filename" on:
commit: b188c57af2b5c17a1e8f71a0358f330446a4f788 ("workqueue: Split alloc_workqueue into internal function and lockdep init")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: boot
compiler: clang-18
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+----------------------------------------+------------+------------+
| | 946c57e61d | b188c57af2 |
+----------------------------------------+------------+------------+
| sysfs:cannot_create_duplicate_filename | 0 | 12 |
+----------------------------------------+------------+------------+
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/202408161132.7c52d91a-oliver.sang@intel.com
[ OK ] Started OpenBSD Secure Shell server.
[ 116.454031][ T134] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
LKP: ttyS0: 211: Kernel tests: Boot OK!
LKP: ttyS0: 211: HOSTNAME vm-snb, MAC 52:54:00:12:34:56, kernel 6.11.0-rc1-00003-gb188c57af2b5 1[ 116.612859][ T177] scsi host0: ata_piix
[ 116.885461][ T177] sysfs: cannot create duplicate filename '/devices/virtual/workqueue/scsi_tmf_7698144'
[ 116.902822][ T177] CPU: 1 UID: 0 PID: 177 Comm: systemd-udevd Not tainted 6.11.0-rc1-00003-gb188c57af2b5 #1
[ 116.919869][ T177] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 116.937535][ T177] Call Trace:
[ 116.952146][ T177] <TASK>
[ 116.958139][ T177] dump_stack_lvl (kbuild/src/consumer/lib/dump_stack.c:121)
[ 116.966343][ T177] sysfs_create_dir_ns (kbuild/src/consumer/fs/sysfs/dir.c:32 kbuild/src/consumer/fs/sysfs/dir.c:63)
[ 116.974637][ T177] kobject_add_internal (kbuild/src/consumer/lib/kobject.c:74 kbuild/src/consumer/lib/kobject.c:240)
[ 116.984066][ T177] kobject_add (kbuild/src/consumer/lib/kobject.c:430)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240816/202408161132.7c52d91a-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-16 4:08 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=202408161132.7c52d91a-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=matthew.brost@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=tj@kernel.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