From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753352AbcITBKj (ORCPT ); Mon, 19 Sep 2016 21:10:39 -0400 Received: from ozlabs.org ([103.22.144.67]:53606 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751685AbcITBKi (ORCPT ); Mon, 19 Sep 2016 21:10:38 -0400 From: Michael Ellerman To: Jan Kara , Guenter Roeck Cc: "linux-kernel\@vger.kernel.org" , Andrew Morton Subject: Re: Crashes in next-20160915 (BUG at fs/notify/notification.c:66!) In-Reply-To: <20160916124948.GG24269@quack2.suse.cz> References: <20160916064521.GF24269@quack2.suse.cz> <6ae57328-ab25-8798-51f9-9a30d9c2af70@roeck-us.net> <20160916124948.GG24269@quack2.suse.cz> User-Agent: Notmuch/0.21 (https://notmuchmail.org) Date: Tue, 20 Sep 2016 11:10:35 +1000 Message-ID: <87vaxrs7ec.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Jan Kara writes: > On Fri 16-09-16 04:10:38, Guenter Roeck wrote: >> On 09/15/2016 11:45 PM, Jan Kara wrote: >> >On Thu 15-09-16 19:20:10, Guenter Roeck wrote: >> >>I see various architectures crashing in -next with the following error. >> >>------------[ cut here ]------------ >> >>kernel BUG at fs/notify/notification.c:66! >> >> >correct" - famous last words ;). I've seen zero-day robot complain as well >> >so I'll try the config it had sent me and see what's going on (likely >> >spin_is_locked() does not do what I thought under some configs...). >> >> Your builds are probably all SMP builds. Looks like this happens if SMP >> is disabled. > > Right, that was the problem. spin_is_locked() without CONFIG_SPINLOCK_DEBUG > returns always 0. Can we get this fixed soon please? It's breaking all my CI runs. cheers