[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-07-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647

Anatoly Pugachev (mator...@gmail.com) changed:

   What|Removed |Added

 CC||mator...@gmail.com

--- Comment #7 from Anatoly Pugachev (mator...@gmail.com) ---
it's the same for sparc64:

`
[0.20] PROMLIB: Sun IEEE Boot Prom 'OBP 4.38.12 2018/03/28 14:54'
[0.32] PROMLIB: Root node compatible: sun4v
[0.80] 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.

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647

Michael Ellerman (mich...@ellerman.id.au) changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||mich...@ellerman.id.au
 Resolution|--- |DOCUMENTED

--- Comment #6 from Michael Ellerman (mich...@ellerman.id.au) ---
This appears to be working as expected, which I admit is a little confusing.

The key thing is that at the end you see, eg:

  [0.179788] Good, all 261 testcases passed! |

See the commit that added the test:

https://git.kernel.org/torvalds/c/e91498589746

  locking/lockdep/selftests: Add mixed read-write ABBA tests

  Currently lockdep has limited support for recursive readers, add a few
  mixed read-write ABBA selftests to show the extend of these
  limitations.

And in the code:

print_testname("mixed read-lock/lock-write ABBA");
pr_cont(" |");
dotest(rlock_ABBA1, FAILURE, LOCKTYPE_RWLOCK);
#ifdef CONFIG_PROVE_LOCKING
/*
 * Lockdep does indeed fail here, but there's nothing we can do about
 * that now.  Don't kill lockdep for it.
 */
unexpected_testcase_failures--;
#endif

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647

--- Comment #5 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 282841
  --> https://bugzilla.kernel.org/attachment.cgi?id=282841=edit
kernel .config (5.1.3, G5 11,2)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647

--- Comment #4 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 282839
  --> https://bugzilla.kernel.org/attachment.cgi?id=282839=edit
dmesg (4.9.177, G5 11,2)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647

--- Comment #3 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 282837
  --> https://bugzilla.kernel.org/attachment.cgi?id=282837=edit
dmesg (4.14.120, G5 11,2)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647

--- Comment #2 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 282835
  --> https://bugzilla.kernel.org/attachment.cgi?id=282835=edit
dmesg (4.19.44, G5 11,2)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 203647] Locking API testsuite fails "mixed read-lock/lock-write ABBA" rlock on kernels >=4.14.x

2019-05-19 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=203647

--- Comment #1 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 282833
  --> https://bugzilla.kernel.org/attachment.cgi?id=282833=edit
dmesg (5.0.17, G5 11,2)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.