From: Robert Hancock <hancockr@shaw.ca>
To: Tobias <kaminsky@finswimmer.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [REQUEST] Option for skipping unreadable blocks on Video DVD
Date: Sat, 17 Nov 2007 22:58:10 -0600 [thread overview]
Message-ID: <473FC662.7020901@shaw.ca> (raw)
In-Reply-To: <fa.DNZjDdh1eNcFR2zDRKzQ6G2bIVU@ifi.uio.no>
Tobias wrote:
> If you are accessing a scratched Video DVD and the device cannot read it, the
> process ends.
> What about a more tolerant way to handle unreadable blocks.
> Especially on Video DVDs single blocks are not that important than on data
> dvds.
If the DVD player process ends from this, I'd say that's the fault of
the player software not handling errors properly.
I think that if they are using the normal block layer accesses on the
DVD device, there may be some retries that occur which are likely
undesirable in this case since they will just stall playback. If they
are using SG_IO to feed raw requests into the drive (which I imagine
they need to do for CSS authentication, etc. anyway), then all error
handling is passed up to the user application.
>
> So is there a way that the kernel tells the device to skip these bad blocks?
We don't know they're bad until we try and read them. How long the drive
will stall trying to read that sector before giving up and returning an
error is up to the drive. I'm not sure if the MMC command set allows any
way to tell the drive to give up more quickly or not..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-11-18 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.DNZjDdh1eNcFR2zDRKzQ6G2bIVU@ifi.uio.no>
2007-11-18 4:58 ` Robert Hancock [this message]
2007-11-18 22:34 ` [REQUEST] Option for skipping unreadable blocks on Video DVD Tobias
2007-11-25 18:32 ` Pavel Machek
2007-11-17 11:29 Tobias
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=473FC662.7020901@shaw.ca \
--to=hancockr@shaw.ca \
--cc=kaminsky@finswimmer.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