Messages in this thread | | | From | Michael Ellerman <> | Subject | Re: Crashes in next-20160915 (BUG at fs/notify/notification.c:66!) | Date | Tue, 20 Sep 2016 11:10:35 +1000 |
| |
Jan Kara <jack@suse.cz> 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
| |