From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 203647] New: Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x
Date: Sun, 19 May 2019 19:34:47 +0000 [thread overview]
Message-ID: <bug-203647-206035@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=203647
Bug ID: 203647
Summary: Locking API testsuite fails "mixed
read-lock/lock-write ABBA" rlock on kernels >=4.14.x
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 5.1.3
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PPC-64
Assignee: platform_ppc-64@kernel-bugs.osdl.org
Reporter: erhard_f@mailbox.org
Regression: No
Created attachment 282831
--> https://bugzilla.kernel.org/attachment.cgi?id=282831&action=edit
dmesg (5.1.3, G5 11,2)
Probably this test fails on ppc64 since it is around. Kernel 4.9.x passes all
tests, since it does not seem to contain "mixed read-lock/lock-write ABBA".
Machine is a PowerMac G5 11,2 running Gentoo Linux ppc64, Big Endian, 4 KiB
pagesize.
[ 0.002051] ------------------------
[ 0.002065] | Locking API testsuite:
[ 0.002079]
----------------------------------------------------------------------------
[ 0.002111] | spin |wlock |rlock |mutex |
wsem | rsem |
[ 0.002142]
--------------------------------------------------------------------------
[ 0.002179] A-A deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.007366] A-B-B-A deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.012471] A-B-B-C-C-A deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.017598] A-B-C-A-B-C deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.022740] A-B-B-C-C-D-D-A deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.027912] A-B-C-D-B-D-D-A deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.033083] A-B-C-D-B-C-D-A deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.038269] double unlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.043319] initialize held: ok | ok | ok | ok |
ok | ok | ok |
[ 0.048379]
--------------------------------------------------------------------------
[ 0.048411] recursive read-lock: | ok |
| ok |
[ 0.049894] recursive read-lock #2: | ok |
| ok |
[ 0.051375] mixed read-write-lock: | ok |
| ok |
[ 0.052859] mixed write-read-lock: | ok |
| ok |
[ 0.054333] mixed read-lock/lock-write ABBA: |FAILED|
| ok |
[ 0.055802] mixed read-lock/lock-read ABBA: | ok |
| ok |
[ 0.057290] mixed write-lock/lock-write ABBA: | ok |
| ok |
[ 0.058771]
--------------------------------------------------------------------------
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2019-05-19 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 19:34 bugzilla-daemon [this message]
2019-05-19 19:35 ` [Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x bugzilla-daemon
2019-05-19 19:35 ` bugzilla-daemon
2019-05-19 19:36 ` bugzilla-daemon
2019-05-19 19:36 ` bugzilla-daemon
2019-05-19 19:37 ` bugzilla-daemon
2019-05-21 5:35 ` bugzilla-daemon
2019-07-16 8:58 ` bugzilla-daemon
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=bug-203647-206035@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).