From: Santiago Garcia Mantinan <manty@xxxxxxxxx>
Date: Wed, 30 Sep 2009 13:05:29 +0200
> [<c010f865>] ? dequeue_task+x90/0x9e
> [<c029d777>] ? schedule+0x2ad/0x2d9
> [<c019f63a>] ? __blk_run_queue+0x39/0x60
> [<c0la4f97>] ? cfq_kick_queue+0x0/0xb
> [<c01a4fa0>] ? cfq_kick_queue+0x9/0xb
> [<c011dd82>] ? worker_thread+0xae/0x11c
So it does look like a normal block I/O request to the disk
going through the CFQ scheduler.
But ->cmd_type of the request is corrupted, but we have no
idea in what way.
Well, we know it's not a special request, because one layer
up the IDE I/O layer driver does special processing for
blk_special_request() by calling ide_special_rq().
I suspect the request structure has been freed already and
we're referencing free'd memory.
Please add this test patch and let us know what messages
you end up with in the logs. It won't BUG() any more,
so you have to watch for the messages.
Thanks!
-DaveM (the IDE bug dodger)
diff --git a/drivers/ide/ide-disk.c b/drivers/ide/ide-disk.c
index 7f87801..54b9dbc 100644
--- a/drivers/ide/ide-disk.c
+++ b/drivers/ide/ide-disk.c
@@ -184,7 +184,11 @@ static ide_startstop_t ide_do_rw_disk(ide_drive_t *drive, struct request *rq,
ide_hwif_t *hwif = drive->hwif;
BUG_ON(drive->dev_flags & IDE_DFLAG_BLOCKED);
- BUG_ON(!blk_fs_request(rq));
+ if (!blk_fs_request(rq)) {
+ pr_alert("IDE: Non-FS req in ide_do_rw_disk(), cmd_type %d\n",
+ rq->cmd_type);
+ ide_kill_rq(drive, rq);
+ }
ledtrig_ide_activity();
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
