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:35:41 -1000 [thread overview]
Message-ID: <ZsYXXd6tQAlFwkg8@slm.duckdns.org> (raw)
In-Reply-To: <ZsYTZTEbtMuVyp1o@slm.duckdns.org>
On Wed, Aug 21, 2024 at 06:18:45AM -1000, Tejun Heo wrote:
...
> > tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 1m --configs "2*TREE01" --trust-make
...
> Hmmm... I have a hard time imagining that change causing that error. My bet
> is unreliable reproducer. I'll try the repro.
I'm probably doing something wrong but all the tests say that init
segfaulted in the log file:
[ 5.505986] init[1]: segfault at 28 ip 000000000040101f sp 00007fff1bbf6fc0 error 4 in init[101f,401000+1000] likely on CPU 12 (core 12, socket 0)
[ 5.509949] Code: Unable to access opcode bytes at 0x400ff5.
[ 5.512314] coredump: 1(init): over coredump resource limit, skipping core dump
[ 5.514976] coredump: 1(init): coredump has not been created, error -7
[ 5.516911] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Pasting the command output:
$ tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 1m --configs "2*TREE01" --trust-make
tools/testing/selftests/rcutorture/initrd/init already exists, no need to create it
Results directory: /home/htejun/os/linux-next/tools/testing/selftests/rcutorture/res/2024.08.21-06.31.03
tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 1m --configs 2*TREE01 --trust-make
----Start batch 1: Wed Aug 21 06:31:03 AM HST 2024
TREE01 8: Starting build. Wed Aug 21 06:31:03 AM HST 2024
TREE01 8: Waiting for build to complete. Wed Aug 21 06:31:03 AM HST 2024
TREE01 8: Build complete. Wed Aug 21 06:31:30 AM HST 2024
TREE01.2 8: Starting build. Wed Aug 21 06:31:30 AM HST 2024
TREE01.2 8: Waiting for build to complete. Wed Aug 21 06:31:30 AM HST 2024
TREE01.2 8: Build complete. Wed Aug 21 06:31:31 AM HST 2024
---- TREE01 8: Kernel present. Wed Aug 21 06:31:31 AM HST 2024
---- TREE01.2 8: Kernel present. Wed Aug 21 06:31:31 AM HST 2024
---- Starting kernels. Wed Aug 21 06:31:31 AM HST 2024
---- All kernel runs complete. Wed Aug 21 06:31:42 AM HST 2024
---- TREE01 8: Build/run results:
--- Wed Aug 21 06:31:03 AM HST 2024: Starting build, PID 456070
--- Wed Aug 21 06:31:31 AM HST 2024: Starting kernel
CPU-hotplug kernel, adding rcutorture onoff.
--- Wed Aug 21 06:31:31 AM HST 2024: Starting kernel, PID 483593
Monitoring qemu job at pid 483623 Wed Aug 21 06:31:41 AM HST 2024
TREE01 no success message, 0 successful version messages
WARNING: Assertion failure in /home/htejun/os/linux-next/tools/testing/selftests/rcutorture/res/2024.08.21-06.31.03/TREE01/console.log TREE01
WARNING: Summary: Call Traces: 1
---- TREE01.2 8: Build/run results:
--- Wed Aug 21 06:31:30 AM HST 2024: Starting build, PID 482122
--- Wed Aug 21 06:31:31 AM HST 2024: Starting kernel
CPU-hotplug kernel, adding rcutorture onoff.
--- Wed Aug 21 06:31:31 AM HST 2024: Starting kernel, PID 483619
Monitoring qemu job at pid 483648 Wed Aug 21 06:31:41 AM HST 2024
TREE01 no success message, 0 successful version messages
WARNING: Assertion failure in /home/htejun/os/linux-next/tools/testing/selftests/rcutorture/res/2024.08.21-06.31.03/TREE01.2/console.log TREE01
WARNING: Summary: Call Traces: 1
--- Wed Aug 21 06:31:42 AM HST 2024 Test summary:
Results directory: /home/htejun/os/linux-next/tools/testing/selftests/rcutorture/res/2024.08.21-06.31.03
tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 1m --configs 2*TREE01 --trust-make
TREE01 -------
TREE01 no success message, 0 successful version messages
WARNING: Assertion failure in /home/htejun/os/linux-next/tools/testing/selftests/rcutorture/res/2024.08.21-06.31.03/TREE01/console.log TREE01
WARNING: Summary: Call Traces: 1
Completed in 10 vs. 60
TREE01.2 -------
TREE01.2 no success message, 0 successful version messages
WARNING: Assertion failure in /home/htejun/os/linux-next/tools/testing/selftests/rcutorture/res/2024.08.21-06.31.03/TREE01.2/console.log TREE01.2
WARNING: Summary: Call Traces: 1
Completed in 10 vs. 60
2 runs with build errors.
2 runs with runtime errors.
--- Done at Wed Aug 21 06:31:42 AM HST 2024 (39 seconds) exitcode 3
--
tejun
next prev parent reply other threads:[~2024-08-21 16:35 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
2024-08-21 16:35 ` Tejun Heo [this message]
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=ZsYXXd6tQAlFwkg8@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®