public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Wed, 20 Apr 2016 11:41:17 +0200	[thread overview]
Message-ID: <20160420094117.GT3408@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <571642BC.9040606@kyup.com>

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.

      reply	other threads:[~2016-04-20  9:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 14:37 Crash in __wake_up_common Nikolay Borisov
2016-04-20  9:41 ` Peter Zijlstra [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160420094117.GT3408@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=kernel@kyup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=operations@siteground.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox