From: Tejun Heo <tj@kernel.org>
To: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
Cc: Kay Sievers <kay.sievers@vrfy.org>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] Problem since "block: make gendisk hold a reference to its queue"
Date: Tue, 10 Jan 2012 08:22:34 -0800 [thread overview]
Message-ID: <20120110162234.GA20446@google.com> (raw)
In-Reply-To: <gik44z4phd.fsf@karga.hank.lab>
Hello,
On Tue, Jan 10, 2012 at 03:11:10PM +0100, Dirk Gouders wrote:
> I noticed problematic kernel messages when my laptop boots, bisecting
> this issue lead me to commit 523e1d399c. I attach the messages that I
> currently (commit e4e11180df) see, please let me know if further
> information is needed.
Thank you very much for bisecting the problem.
> floppy0: no floppy controllers found
> =============================================================================
> BUG blkdev_queue: Poison overwritten
> -----------------------------------------------------------------------------
Yeah, floppy does some funky stuff during init.
> Object ffff88006ec30420: 6b 6b 6b 6b 6b 6b 6b 6b 6a 6b 6b 6b 6b 6b 6b 6b kkkkkkkkjkkkkkkk
This looks like refcnt is dec'd after released. Can you please apply
the following patch and see whether the WARN_ON() triggers?
diff --git a/block/blk-core.c b/block/blk-core.c
index 15de223..c3de15e 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -342,6 +342,7 @@ EXPORT_SYMBOL(blk_run_queue);
void blk_put_queue(struct request_queue *q)
{
+ WARN_ON(atomic_read(&q->kobj.kref.refcount) == 0x6b6b6b6b);
kobject_put(&q->kobj);
}
EXPORT_SYMBOL(blk_put_queue);
next prev parent reply other threads:[~2012-01-10 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 14:11 [BUG] Problem since "block: make gendisk hold a reference to its queue" Dirk Gouders
2012-01-10 16:22 ` Tejun Heo [this message]
2012-01-10 17:10 ` Dirk Gouders
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=20120110162234.GA20446@google.com \
--to=tj@kernel.org \
--cc=gouders@et.bocholt.fh-gelsenkirchen.de \
--cc=kay.sievers@vrfy.org \
--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