From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S933314AbcDTJl2 (ORCPT <rfc822;w@1wt.eu>);
	Wed, 20 Apr 2016 05:41:28 -0400
Received: from merlin.infradead.org ([205.233.59.134]:37803 "EHLO
	merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S932079AbcDTJl0 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 20 Apr 2016 05:41:26 -0400
Date: Wed, 20 Apr 2016 11:41:17 +0200
From: Peter Zijlstra <peterz@infradead.org>
To: Nikolay Borisov <kernel@kyup.com>
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
        SiteGround Operations <operations@siteground.com>
Subject: Re: Crash in __wake_up_common
Message-ID: <20160420094117.GT3408@twins.programming.kicks-ass.net>
References: <571642BC.9040606@kyup.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <571642BC.9040606@kyup.com>
User-Agent: Mutt/1.5.21 (2012-12-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Apr 19, 2016 at 05:37:48PM +0300, Nikolay Borisov wrote:
> 
> ffffffff810e08be points to this line in __wake_up_common:
>         list_for_each_entry_safe(curr, next, &q->task_list, task_list) {
> 
> This is the wait_queue_head_t: 
> 
> crash> struct wait_queue_head_t ffff880438ef52c8
> struct wait_queue_head_t {
>   lock = {
>     {
>       rlock = {
>         raw_lock = {
>           val = {
>             counter = 1
>           }
>         }
>       }
>     }
>   }, 
>   task_list = {
>     next = 0x0, 
>     prev = 0xffff880438ef52d8
>   }
> }
> 
> nr_exclusive seems to be 1, and mode is 3 (TASK_NORMAL). 
> 
> The spl module is coming from zfs(ZoL) but I dunno whether this might 
> be a bug in the scheduler or in the zfs. The line which led to the 
> __wake_up is this: 
> 
> wake_up(&tq->tq_wait_waitq);

Given that the waitqueue code is rather widely used, I suspect this is a
fail in zfs. But given the license issues I'm not going near that code.