From: John Snow <jsnow@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Cc: stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] ide: Check validity of logical block size
Date: Wed, 03 Dec 2014 09:45:15 -0500 [thread overview]
Message-ID: <547F21FB.1050009@redhat.com> (raw)
In-Reply-To: <1417610103-18234-1-git-send-email-kwolf@redhat.com>
On 12/03/2014 07:35 AM, Kevin Wolf wrote:
> Our IDE emulation can't handle logical block sizes other than 512. Check
> for it.
>
> The original assumption was that other values would silently be ignored
> (which is bad enough), but it's not quite true: The physical block size
> is exposed in IDENTIFY DEVICE as a multiple of the logical block size.
> Setting a logical block size therefore also corrupts the physical block
> size (4096/4096 doesn't silently downgrade to 4096/512, but 512/512).
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> hw/ide/qdev.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/hw/ide/qdev.c b/hw/ide/qdev.c
> index b4f096e..1ebb58d 100644
> --- a/hw/ide/qdev.c
> +++ b/hw/ide/qdev.c
> @@ -163,6 +163,11 @@ static int ide_dev_initfn(IDEDevice *dev, IDEDriveKind kind)
> return -1;
> }
>
> + if (dev->conf.logical_block_size != 512) {
> + error_report("logical_block_size must be 512 for IDE");
> + return -1;
> + }
> +
> blkconf_serial(&dev->conf, &dev->serial);
> if (kind != IDE_CD) {
> blkconf_geometry(&dev->conf, &dev->chs_trans, 65536, 16, 255, &err);
>
There are so many 512 literals in the IDE code that I actually assumed
we already enforced this, or otherwise just always used 512 regardless.
Reviewed-by: John Snow <jsnow@redhat.com>
next prev parent reply other threads:[~2014-12-03 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 12:35 [Qemu-devel] [PATCH] ide: Check validity of logical block size Kevin Wolf
2014-12-03 14:37 ` Markus Armbruster
2014-12-03 14:50 ` Kevin Wolf
2014-12-03 14:45 ` John Snow [this message]
2014-12-03 14:53 ` Kevin Wolf
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=547F21FB.1050009@redhat.com \
--to=jsnow@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).