Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1383227

Re: Crash in __wake_up_common

Path csiph.com!news.mixmin.net!weretis.net!feeder4.news.weretis.net!storethat.news.telefonica.de!telefonica.de!news.panservice.it!bofh.it!news.nic.it!robomod
From Peter Zijlstra <peterz@infradead.org>
Newsgroups linux.kernel
Subject Re: Crash in __wake_up_common
Date Wed, 20 Apr 2016 11:50:02 +0200
Message-ID <rpWVI-5LM-29@gated-at.bofh.it> (permalink)
References <rpEYO-8k2-35@gated-at.bofh.it>
X-Original-To Nikolay Borisov <kernel@kyup.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
User-Agent Mutt/1.5.21 (2012-12-30)
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 36
Organization linux.* mail to news gateway
X-Original-Cc "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>, SiteGround Operations <operations@siteground.com>
X-Original-Date Wed, 20 Apr 2016 11:41:17 +0200
X-Original-Message-ID <20160420094117.GT3408@twins.programming.kicks-ass.net>
X-Original-References <571642BC.9040606@kyup.com>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1383227

Show key headers only | View raw


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.

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Crash in __wake_up_common Nikolay Borisov <kernel@kyup.com> - 2016-04-19 16:40 +0200
  Re: Crash in __wake_up_common Peter Zijlstra <peterz@infradead.org> - 2016-04-20 11:50 +0200

csiph-web