All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Xin Zhao <jackzxcui1989@163.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-serial@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [tty]  d000422a46: sysfs:cannot_create_duplicate_filename
Date: Wed, 28 Jan 2026 22:09:48 +0800	[thread overview]
Message-ID: <202601282134.b947eae9-lkp@intel.com> (raw)



Hello,

kernel test robot noticed "sysfs:cannot_create_duplicate_filename" on:

commit: d000422a46aad32217cf1be747eb61d641baae2f ("tty: tty_port: add workqueue to flip TTY buffer")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

[test failed on linux-next/master 615aad0f61e0c7a898184a394dc895c610100d4f]

in testcase: boot

config: x86_64-randconfig-003-20260127
compiler: clang-20
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G

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



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/202601282134.b947eae9-lkp@intel.com



[   90.273010][    T1] gpio_winbond: not an our chip
[   90.276100][    T1] ledtrig-cpu: registered to indicate activity on CPUs
[   90.315441][    T1] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[   90.322749][    T1] 00:04: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
[   90.330210][    T1] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[   90.348052][    T1] sysfs: cannot create duplicate filename '/devices/virtual/workqueue/ttyS-flip-wq'
[   90.352197][    T1] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.19.0-rc3-00049-gd000422a46aa #1 VOLUNTARY  96515dc2651f95070d1b72690dc313e8c588745e
[   90.352235][    T1] Call Trace:
[   90.352248][    T1]  <TASK>
[   90.352300][    T1]  __dump_stack (kbuild/src/consumer/lib/dump_stack.c:95)
[   90.352413][    T1]  dump_stack_lvl (kbuild/src/consumer/lib/dump_stack.c:123 (discriminator 1))
[   90.352430][    T1]  dump_stack (kbuild/src/consumer/lib/dump_stack.c:130)
[   90.352440][    T1]  sysfs_warn_dup (kbuild/src/consumer/fs/sysfs/dir.c:32)


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



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


                 reply	other threads:[~2026-01-28 14:10 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=202601282134.b947eae9-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jackzxcui1989@163.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    /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.