From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Jack Howarth <howarth@bromo.msbb.uc.edu>, linux-kernel@vger.kernel.org
Subject: Re: why no option for 'ide=nocddma'?
Date: Thu, 30 Mar 2006 11:37:28 +0100 [thread overview]
Message-ID: <1143715048.29388.22.camel@localhost.localdomain> (raw)
In-Reply-To: <58cb370e0603300110p43c33040hdb95a8c871f4b50d@mail.gmail.com>
On Iau, 2006-03-30 at 11:10 +0200, Bartlomiej Zolnierkiewicz wrote:
> EOF handling error has nothing to do with IDE layer,
> the same problem can be reproduced using libata+PATA patches.
I've never been able to reproduce it with libata+PATA patches, with
ide-scsi or with scsi devices. One clear reason for that is they handle
partial write returns correctly which unpatched drivers/ide does not.
So ide-cd goes "Read 64K" and the CD goes "umm erp splat have 8K" and
it tells the block layer "failed". ide-scsi goes "here is 8K, fail 56K"
and also adjusts the volume size (without proper locking)
The underlying problem is the block layer certainly but ide-cd is an
offender too. One simple hack for ide-cd would be to return success and
fill the excess buffer space with "JensAxboeAteMyComputer"[1] or similar
as padding providing the write fail is coming from end of media in the
last 150K or so.
Alan
[1] I'm kidding about this, zero would be the right padding.
next prev parent reply other threads:[~2006-03-30 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 18:43 Jack Howarth
2006-03-26 18:07 ` Alan Cox
2006-03-30 9:10 ` Bartlomiej Zolnierkiewicz
2006-03-30 10:37 ` Alan Cox [this message]
2006-03-30 14:27 Jack Howarth
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=1143715048.29388.22.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=howarth@bromo.msbb.uc.edu \
--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
Powered by JetHome