mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: Jens Axboe <axboe@kernel.dk>, linux-kernel@vger.kernel.org
Subject: Re: WARNING: at block/genhd.c:1556 disk_clear_events+0xdc/0xf0()
Date: Thu, 21 Apr 2011 19:38:45 +0200	[thread overview]
Message-ID: <20110421173845.GE15988@htj.dyndns.org> (raw)
In-Reply-To: <20110415214140.GB1295@sucs.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

  reply	other threads:[~2011-04-21 17:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 21:16 Sitsofe Wheeler
2011-04-05  1:51 ` Jens Axboe
2011-04-06 13:04 ` Tejun Heo
2011-04-06 21:26   ` Sitsofe Wheeler
2011-04-06 21:37     ` Tejun Heo
2011-04-09  9:34       ` Sitsofe Wheeler
2011-04-10 14:59         ` Sitsofe Wheeler
2011-04-13 20:00           ` Tejun Heo
2011-04-15  9:01             ` Tejun Heo
2011-04-15 18:20               ` Tejun Heo
2011-04-15 21:41                 ` Sitsofe Wheeler
2011-04-21 17:38                   ` Tejun Heo [this message]
2011-04-21 18:43                     ` Tejun Heo
2011-05-10 16:48                       ` Tejun Heo

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=20110421173845.GE15988@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sitsofe@yahoo.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

all inboxes | Powered by JetHome®