From: Stefan Hajnoczi <stefanha@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] ide: refuse WIN_READ_NATIVE_MAX on empty device
Date: Fri, 5 Apr 2013 16:07:18 +0200 [thread overview]
Message-ID: <CAJSP0QUHw6rRxdhEF1D9gD2OYwzoO3P2jFAn+Nus0xjsPSPNqw@mail.gmail.com> (raw)
In-Reply-To: <87mwtdkudb.fsf@blackfin.pond.sub.org>
On Fri, Apr 5, 2013 at 2:57 PM, Markus Armbruster <armbru@redhat.com> wrote:
> Stefan Hajnoczi <stefanha@redhat.com> writes:
>
>> On Fri, Apr 05, 2013 at 12:56:07PM +0200, Markus Armbruster wrote:
>>> Stefan Hajnoczi <stefanha@redhat.com> writes:
>>>
>>> > What is the highest addressable sector on an empty CD-ROM? Nothing is
>>> > addressable so produce an error.
>>> >
>>> > This patch prevents a divide-by-zero in ide_set_sector() since
>>> > s->sectors and s->heads would be 0. Not to mention that a sector=-1
>>> > argument would be nonsense.
>>> >
>>> > Note that WIN_READ_NATIVE_MAX can be triggered using hdparm -N 1024
>>> > /dev/cdrom. The LBA bit will be set to 1 though, so the only easy way
>>> > to go down the ide_set_sector() CHS code path which divides by zero is
>>> > to comment out the s->select & 0x40 case for testing.
>>>
>>> Suggests you did that.
>>>
>>> Have you tried the reproducer with a physical drive? Does it fail the
>>> command when empty, too?
>>
>> Believe it or not, I don't have access to an ATAPI CD-ROM drive. Would
>> you be able to try out hdparm -N 1024 /dev/cdrom?
>>
>> Note that READ NATIVE MAX is optional, real drives may not implement it
>> since it seems geared towards the Host Protected Area feature which
>> makes no sense on CD-ROMs. (The idea is a reserved area on the disk
>> where system data can be stored and the OS will not touch it.)
>>
>> Stefan
>
> # hdparm -N /dev/cdrom
>
> /dev/cdrom:
> READ_NATIVE_MAX_ADDRESS failed: Input/output error
> # hdparm -N 1024 /dev/cdrom
>
> /dev/cdrom:
> setting max visible sectors to 1024 (temporary)
> READ_NATIVE_MAX_ADDRESS failed: Input/output error
> READ_NATIVE_MAX_ADDRESS failed: Input/output error
>
> Same with and without media.
>
> If the command makes no sense for CD-ROMs, and generally isn't
> implemented by them, we should consider not implementing either, by
> clearing its IDE_CD bit in ide_cmd_table.
Thank you!
You're getting the same result that we get in the guest. This looks good.
There's no harm in supporting READ NATIVE MAX when the CD-ROM is
inserted. It's basically another way of finding out the block device
size.
I also like this fix better than blacklisting the command since it now
protects us in case HD or CFA devices ever have nb_sectors = 0 too.
In other words, it's more defensive than just fixing CD-ROMs.
Stefan
next prev parent reply other threads:[~2013-04-05 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 9:51 [Qemu-devel] [PATCH] ide: refuse WIN_READ_NATIVE_MAX on empty device Stefan Hajnoczi
2013-04-05 10:56 ` Markus Armbruster
2013-04-05 12:19 ` Stefan Hajnoczi
2013-04-05 12:57 ` Markus Armbruster
2013-04-05 14:07 ` Stefan Hajnoczi [this message]
2013-04-05 15:11 ` Markus Armbruster
2013-04-10 9:08 ` Stefan Hajnoczi
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=CAJSP0QUHw6rRxdhEF1D9gD2OYwzoO3P2jFAn+Nus0xjsPSPNqw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).