Re: WARNING in __mutex_unlock_slowpath

2018-05-08 Thread Roman Kagan
On Mon, May 07, 2018 at 07:19:04PM +0200, Paolo Bonzini wrote: > On 29/04/2018 19:00, syzbot wrote: > > syzbot hit the following crash on upstream commit > > bf8f5de17442bba5f811e7e724980730e079ee11 (Sat Apr 28 17:05:04 2018 +) > > MAINTAINERS: add myself as maintainer of AFFS > > syzbot dashbo

Re: WARNING in __mutex_unlock_slowpath

2018-05-08 Thread Paolo Bonzini
On 07/05/2018 23:49, Tetsuo Handa wrote: > On 2018/05/08 2:19, Paolo Bonzini wrote: >>> [ cut here ] >>> DEBUG_LOCKS_WARN_ON(__owner_task(owner) != current) >>> WARNING: CPU: 0 PID: 4525 at kernel/locking/mutex.c:1032 >>> __mutex_unlock_slowpath+0x62e/0x8a0 kernel/locking/mu

Re: WARNING in __mutex_unlock_slowpath

2018-05-07 Thread Tetsuo Handa
On 2018/05/08 2:19, Paolo Bonzini wrote: >> [ cut here ] >> DEBUG_LOCKS_WARN_ON(__owner_task(owner) != current) >> WARNING: CPU: 0 PID: 4525 at kernel/locking/mutex.c:1032 >> __mutex_unlock_slowpath+0x62e/0x8a0 kernel/locking/mutex.c:1032 >> Kernel panic - not syncing: panic

Re: WARNING in __mutex_unlock_slowpath

2018-05-07 Thread Paolo Bonzini
On 07/05/2018 19:31, Dmitry Vyukov wrote: > May be related to: > > https://syzkaller.appspot.com/bug?id=aec313f3f7ebc2ee0abb1104a3631ab8fd1e90f2 > Yeah, most likely. Paolo

Re: WARNING in __mutex_unlock_slowpath

2018-05-07 Thread Dmitry Vyukov
On Mon, May 7, 2018 at 7:19 PM, Paolo Bonzini wrote: > On 29/04/2018 19:00, syzbot wrote: >> Hello, >> >> syzbot hit the following crash on upstream commit >> bf8f5de17442bba5f811e7e724980730e079ee11 (Sat Apr 28 17:05:04 2018 +) >> MAINTAINERS: add myself as maintainer of AFFS >> syzbot dashbo

Re: WARNING in __mutex_unlock_slowpath

2018-05-07 Thread Paolo Bonzini
On 29/04/2018 19:00, syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > bf8f5de17442bba5f811e7e724980730e079ee11 (Sat Apr 28 17:05:04 2018 +) > MAINTAINERS: add myself as maintainer of AFFS > syzbot dashboard link: > https://syzkaller.appspot.com/bug?extid=35666cba7