From: Jens Axboe <axboe@suse.de>
To: Carl Ritson <critson@perlfu.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS: 2.5.1-pre8 - cdrecord + ide_scsi
Date: Sun, 9 Dec 2001 11:31:04 +0100 [thread overview]
Message-ID: <20011209103104.GD20061@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0112090919220.1468-100000@eden.lincnet> <20011209102208.GC20061@suse.de>
In-Reply-To: <20011209102208.GC20061@suse.de>
On Sun, Dec 09 2001, Jens Axboe wrote:
> On Sun, Dec 09 2001, Carl Ritson wrote:
> > Got this at the very start of burning a cd, nothing special, using
> > ide-scsi build into kernel. "cdrecord -v dev=0,0,0 speed=4 img.iso".
> > Box is Dual-PIII 866, 1GB Ram, all IDE system.
>
> Agrh, because of a bug in ide-scsi conversion this (other) bug went
> unnoticed for a while. Basically we cannot look up the request queue
> reliably from a request, since it may not have originated from the block
> layer. ide-scsi builds it's own, for example. For those, we don't want
> to trust the sg count either.
>
> Does attached patch work?
Irk, there's a ide-scsi bug in there too. In
drivers/scsi/ide-scsi.c:idescsi_free_bio() change the kfree(bhp) to
bio_put(bhp)
--
Jens Axboe
next prev parent reply other threads:[~2001-12-09 10:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 9:26 OOPS: 2.5.1-pre8 - cdrecord + ide_scsi Carl Ritson
2001-12-09 10:22 ` Jens Axboe
2001-12-09 10:31 ` Jens Axboe [this message]
2001-12-09 13:52 ` Carl Ritson
2001-12-09 13:58 ` Jens Axboe
2001-12-09 15:35 ` Carl Ritson
2001-12-09 15:38 ` Jens Axboe
2001-12-11 14:28 ` Jens Axboe
2001-12-12 8:02 ` Carl Ritson
2001-12-12 9:38 ` Jens Axboe
2001-12-15 0:06 ` Andre Hedrick
2001-12-15 10:13 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2001-12-15 15:03 Thomas Hood
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=20011209103104.GD20061@suse.de \
--to=axboe@suse.de \
--cc=critson@perlfu.co.uk \
--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