mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: matthew.brost@intel.com, jiangshanlai@gmail.com,
	sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org
Subject: Re: [BUG bisected] sysfs: cannot create duplicate filename '/devices/virtual/workqueue/scsi_tmf_1073822488'
Date: Wed, 21 Aug 2024 06:18:45 -1000	[thread overview]
Message-ID: <ZsYTZTEbtMuVyp1o@slm.duckdns.org> (raw)
In-Reply-To: <8d443293-2020-42d9-b5b1-1348f551648f@paulmck-laptop>

On Tue, Aug 20, 2024 at 07:16:00PM -0700, Paul E. McKenney wrote:
> Running rcutorture scenario TREE01 on next-20240820 on a dual-socket x86
> system (and for that matter on my laptop) got me this warning during boot:
> 
> sysfs: cannot create duplicate filename '/devices/virtual/workqueue/scsi_tmf_1073822488'
> 
> The number at the end varies from run to run.
> 
> Bisection landed here:
> 
> b188c57af2b5 ("workqueue: Split alloc_workqueue into internal function and lockdep init")
> 
> My reproducer is to run this at the top of the Linux-kernel file tree:
> 
> tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 1m --configs "2*TREE01" --trust-make
> 
> Reverting this commit on top of next-20240820 gets me clean runs.
> 
> I cannot see how the patch would make this happen, but then again,
> I don't know this code at all well.
> 
> Thoughts?

Hmmm... I have a hard time imagining that change causing that error. My bet
is unreliable reproducer. I'll try the repro.

Thanks.

-- 
tejun

  reply	other threads:[~2024-08-21 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21  2:16 Paul E. McKenney
2024-08-21 16:18 ` Tejun Heo [this message]
2024-08-21 16:35   ` Tejun Heo
2024-08-21 17:37     ` Paul E. McKenney
2024-08-21 18:14       ` Paul E. McKenney

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=ZsYTZTEbtMuVyp1o@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=paulmck@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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
all inboxes | Powered by JetHome®