From: Tejun Heo <tj@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Jens Axboe <jaxboe@fusionio.com>
Subject: Re: block: WARN_ON_ONCE(ev->block <= 0) triggered in __disk_unblock_events()
Date: Tue, 3 Jan 2012 10:37:41 -0800 [thread overview]
Message-ID: <20120103183741.GE31746@google.com> (raw)
In-Reply-To: <CAO+b5-pig48acSXAYKH09QHCL9EtzTis=mpn=OnE=cvCv+0EzA@mail.gmail.com>
Hello,
On Sun, Jan 01, 2012 at 05:22:58PM +0000, Bart Van Assche wrote:
> In a workload that involves a lot of scsi_remove_hosts() calls (srp-ha
> patch set stress test) I get the call stack below after about 30 to 50
> iterations. Is this a known issue ? Does this indicate a race
> condition in the block layer ? I can trigger this issue not only with
> 3.2-rc7 but also with 3.1.6. I haven't tried any other kernel versions
> yet.
>
> ------------[ cut here ]------------
> WARNING: at block/genhd.c:1466 __disk_unblock_events+0xf5/0x110()
It's indicating that there were more disk_unblock_events() than
disk_block_events(). Hmmm... weird. I'll prep a debug patch.
Thanks.
--
tejun
next prev parent reply other threads:[~2012-01-03 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-01 17:22 Bart Van Assche
2012-01-03 18:37 ` Tejun Heo [this message]
2012-01-03 20:33 ` Bart Van Assche
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=20120103183741.GE31746@google.com \
--to=tj@kernel.org \
--cc=bvanassche@acm.org \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome