From: Jens Axboe <jens.axboe@oracle.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [bug - scsi/blk] -git, WARNING: at include/linux/blkdev.h:427 __blk_run_queue+0x74/0xa0()
Date: Tue, 29 Apr 2008 22:04:20 +0200 [thread overview]
Message-ID: <20080429200419.GF12774@kernel.dk> (raw)
In-Reply-To: <20080429195508.GA30109@elte.hu>
On Tue, Apr 29 2008, Ingo Molnar wrote:
>
> x86.git auto-testing found two new warnings below with latest -git:
>
> WARNING: at include/linux/blkdev.h:439 blk_remove_plug+0x69/0x80()
> WARNING: at include/linux/blkdev.h:427 __blk_run_queue+0x74/0xa0()
>
> one seems a relatively harmless init locking bug (unlocked access in a
> probe function), the other seems scarier as it happens in an irq handler
> and it likely would trigger multiple times if it wasnt a WARN_ON_ONCE().
>
> Config and full log at:
>
> http://redhat.com/~mingo/misc/log-Tue_Apr_29_21_40_46_CEST_2008.bad
> http://redhat.com/~mingo/misc/config-Tue_Apr_29_21_40_46_CEST_2008.bad
404 on those, but I think Bart and I already closed this one:
diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
index 669b65c..9e2e23b 100644
--- a/include/linux/blkdev.h
+++ b/include/linux/blkdev.h
@@ -418,8 +418,12 @@ struct request_queue
static inline int queue_is_locked(struct request_queue *q)
{
+#ifdef CONFIG_SMP
spinlock_t *lock = q->queue_lock;
return lock && spin_is_locked(lock);
+#else
+ return 1;
+#endif
}
static inline void queue_flag_set_unlocked(unsigned int flag,
--
Jens Axboe
next prev parent reply other threads:[~2008-04-29 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 19:55 [bug - scsi/blk] -git, WARNING: at include/linux/blkdev.h:427 __blk_run_queue+0x74/0xa0() Ingo Molnar
2008-04-29 20:04 ` Jens Axboe [this message]
2008-04-29 20:55 ` Ingo Molnar
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=20080429200419.GF12774@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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