From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x
Date: Tue, 16 Jul 2019 08:58:37 +0000 [thread overview]
Message-ID: <bug-203647-206035-0zdwA3O9aN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203647-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203647
Anatoly Pugachev (matorola@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matorola@gmail.com
--- Comment #7 from Anatoly Pugachev (matorola@gmail.com) ---
it's the same for sparc64:
`
[ 0.000020] PROMLIB: Sun IEEE Boot Prom 'OBP 4.38.12 2018/03/28 14:54'
[ 0.000032] PROMLIB: Root node compatible: sun4v
[ 0.000080] Linux version 5.2.0-10808-g9637d517347e (mator@ttip) (gcc
version 8.3.0 (Debian 8.3.0-7)) #1080 SMP Tue Jul 16 10:46:19 MSK 2019
[ 0.000386] printk: bootconsole [earlyprom0] enabled
[ 0.000441] ARCH: SUN4V
...
[ 0.451068] memory used by lock dependency info: 3855 kB
[ 0.451104] per task-struct memory footprint: 1920 bytes
[ 0.451140] ------------------------
[ 0.451167] | Locking API testsuite:
[ 0.451194]
----------------------------------------------------------------------------
[ 0.451244] | spin |wlock |rlock |mutex |
wsem | rsem |
[ 0.451294]
--------------------------------------------------------------------------
[ 0.451350] A-A deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.454281] A-B-B-A deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.457443] A-B-B-C-C-A deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.460744] A-B-C-A-B-C deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.464032] A-B-B-C-C-D-D-A deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.467545] A-B-C-D-B-D-D-A deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.471009] A-B-C-D-B-C-D-A deadlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.474475] double unlock: ok | ok | ok | ok |
ok | ok | ok |
[ 0.477425] initialize held: ok | ok | ok | ok |
ok | ok | ok |
[ 0.480301]
--------------------------------------------------------------------------
[ 0.480352] recursive read-lock: | ok |
| ok |
[ 0.481247] recursive read-lock #2: | ok |
| ok |
[ 0.482120] mixed read-write-lock: | ok |
| ok |
[ 0.482998] mixed write-read-lock: | ok |
| ok |
[ 0.483878] mixed read-lock/lock-write ABBA: |FAILED|
| ok |
[ 0.484755] mixed read-lock/lock-read ABBA: | ok |
| ok |
[ 0.485676] mixed write-lock/lock-write ABBA: | ok |
| ok |
[ 0.486597]
--------------------------------------------------------------------------
`
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2019-07-16 9:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 19:34 [Bug 203647] New: Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x bugzilla-daemon
2019-05-19 19:35 ` [Bug 203647] " 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 [this message]
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-0zdwA3O9aN@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).