Re: WARN_ON_ONCE(!new_owner) within wake_futex_pi() triggered

2018-11-29 Thread Heiko Carstens
On Wed, Nov 28, 2018 at 03:32:45PM +0100, Thomas Gleixner wrote: > Heiko, > > On Tue, 27 Nov 2018, Heiko Carstens wrote: > > > with the glibc self-tests I was able to trigger the "this should not > > happen" warning ;) below on s390 (with panic_on_warn=1 set). It looks > > like it is hardly

Re: WARN_ON_ONCE(!new_owner) within wake_futex_pi() triggered

2018-11-28 Thread Thomas Gleixner
Heiko, On Tue, 27 Nov 2018, Heiko Carstens wrote: > with the glibc self-tests I was able to trigger the "this should not > happen" warning ;) below on s390 (with panic_on_warn=1 set). It looks > like it is hardly reproducible. Any idea which self-test triggered that? > This one happened with

WARN_ON_ONCE(!new_owner) within wake_futex_pi() triggered

2018-11-27 Thread Heiko Carstens
Hello, with the glibc self-tests I was able to trigger the "this should not happen" warning ;) below on s390 (with panic_on_warn=1 set). It looks like it is hardly reproducible. This one happened with commit d146194f31c9 for compiling the kernel. Config can be re-created with "make ARCH=s390