From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754859Ab1DURiv (ORCPT ); Thu, 21 Apr 2011 13:38:51 -0400 Received: from mail-fx0-f46.google.com ([209.85.161.46]:48966 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753000Ab1DURit (ORCPT ); Thu, 21 Apr 2011 13:38:49 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=YQfCQo6WizkYT2VqPGbfvVET0HGS36WQqEIxyna0/RP3tLjTQVgDsb/YPo6yCJNj4h ICRlngUzMnnLwWWCCFBJmTIyfJsYH9Dt3L2si8UNQfCR0qs4cHUv9C6ECfaBCzA0Gnqb vMhR4IhPo+43oldl43yPFzGhb5nQSJP5v2WTA= Date: Thu, 21 Apr 2011 19:38:45 +0200 From: Tejun Heo To: Sitsofe Wheeler Cc: Jens Axboe , linux-kernel@vger.kernel.org Subject: Re: WARNING: at block/genhd.c:1556 disk_clear_events+0xdc/0xf0() Message-ID: <20110421173845.GE15988@htj.dyndns.org> References: <20110404211604.GB6133@sucs.org> <20110406130423.GE4142@mtj.dyndns.org> <20110406212611.GA5131@sucs.org> <20110406213718.GA14139@mtj.dyndns.org> <20110409093449.GA10016@sucs.org> <20110410145920.GA3408@sucs.org> <20110413200000.GG3987@mtj.dyndns.org> <20110415090118.GA3315@mtj.dyndns.org> <20110415182006.GA15916@mtj.dyndns.org> <20110415214140.GB1295@sucs.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110415214140.GB1295@sucs.org> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Fri, Apr 15, 2011 at 10:41:40PM +0100, Sitsofe Wheeler wrote: > I couldn't reproduce the problem with the very latest kernel but here's > the output that appeared with an older kernel with your patch: > > ------------[ cut here ]------------ > WARNING: at block/genhd.c:1561 disk_clear_events+0x164/0x170() Hmmm... that's really weird. It indicates that the workqueue command sequence there doesn't guarantee scheduling and completion of the work item, which means either there's a bug in workqueue itself or I'm confused about what's going on. Hopefully, the latter. Unfortunately, even with physical setup, I'm having problem reproducing the problem. Which kernel version are you using exactly? Can you please let me know the commit ID? Thanks. -- tejun