mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Csaba Halasz" <Jester01@freemail.hu>
To: "'Jens Axboe'" <axboe@suse.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: PROBLEM: ide-cd panic with faulty disk and DMA enabled (2.6.0-test9)
Date: Tue, 11 Nov 2003 14:57:19 +0100	[thread overview]
Message-ID: <9B4E9DA25A3DD41189B000508B5C0CEE2142B0@BOMBA> (raw)
In-Reply-To: <9B4E9DA25A3DD41189B000508B5C0CEE29370C@BOMBA>

Hi!

I did some more experimenting last night, and I think
I have stumbled upon something. Don't know
what it means or how to fix it though :)

The request is indeed freed by cdrom_end_request.
The reason is that rq->nr_sectors is an insane value.
And that is because restore_request screwed up.

Just before the crash, in restore_request (ide-cd.c:1346 or so):

restore_request: rq = 0xde158f60, rq->buffer = 0x00000000, bio_data(rq->bio) = 0xc654b000, n=1889704
restore_request: dev hdd: flags = REQ_CMD REQ_STARTED 
sector 7043336, nr/cnr 240/8
bio de09e610, biotail de09e720, buffer 00000000, data 00000000, len 1515870810

The rq->nr_sectors value of 240 will be adjusted to 1889944!
The fix might be as simple as checking for a NULL rq->buffer, but
I don't really understand what is going on here.

Also, somebody else seems to mess with rq->nr_sectors as well,
because I have added a sanity check to cdrom_read_intr and
it catches another such bug, but this time with no preceding
restore_request call...

Hope this helps.

I have also tried ide-scsi, that crashes spectacularly as well.
But I'll start a new thread for that :-)

Greets,
	Csaba


       reply	other threads:[~2003-11-11 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9B4E9DA25A3DD41189B000508B5C0CEE29370C@BOMBA>
2003-11-11 13:57 ` Csaba Halasz [this message]
2003-11-10 15:34 Csaba Halasz
2003-11-10 15:39 ` Jens Axboe
2003-11-10 16:18   ` Jens Axboe

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=9B4E9DA25A3DD41189B000508B5C0CEE2142B0@BOMBA \
    --to=jester01@freemail.hu \
    --cc=axboe@suse.de \
    --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

all inboxes | Powered by JetHome®